Re: problems with gnu screen within console
On Sun, Jun 1, 2008 at 5:31 PM, Tony R Quilkey <trq@iinet.net.au> wrote:
> Arvind Marathe wrote:
>>
>> On Sun, Jun 1, 2008 at 4:34 PM, Steve Lamb <grey@dmiyu.org> wrote:
>>>
>>> Arvind Marathe wrote:
>>>>
>>>> The user (i.e. myself) launching 'startx' has no problems with screen
>>>> within xterm in icewm. But if i 'su' to root or any other user within
>>>> xterm, and try to launch screen, all the errors appear.
>>>
>>> The PATH for the other user(s) and console is not being set.
>>
>> Where or how do i set it? And since i could do all these operations
>> till about a month back, what could have unset these paths?
>>
>> Arvind
>>
>>
>
> I believe your $PATH variable is set within /etc/profile and can be further
> customised within ~/.bashrc
At console, echo $PATH gives
------------------------------------------------------------
/opt/intel/cc/10.1.008/bin:/opt/intel/fc/10.1.008/bin:/usr/soft/crystallographic-packages/coot-0.27/bin:/usr/soft/crystallographic-packages/CNS/cns_solve_1.1//intel-i686-linux_g77/bin:/usr/soft/crystallographic-packages/CNS/cns_solve_1.1//intel-i686-linux_g77/utils:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/soft/crystallographic-packages/ccp4-5.99.1/etc:/usr/soft/crystallographic-packages/ccp4-5.99.1/bin:/usr/soft/crystallographic-packages/ccp4-5.99.1/ccp4i/bin:/usr/soft/inhouse_programs/nuparm:/usr/soft/inhouse_programs/nucgen:/usr/soft/inhouse_programs/nucrad:/usr/soft/inhouse_programs/curvefit:/usr/soft/inhouse_programs/helanal:/usr/soft/inhouse_programs/lsfit:/usr/soft/AMBER/amber9//exe:/home/arvind/bin
------------------------------------------------------------
Most of them are what i have set, but
/usr/local/bin:/usr/bin:/bin:/usr/games
are exported from /etc/profile. Only when i launch screen, they are
not being exported. So why are they getting unset on launching screen
within console? And how do i reset them?
And as i mentioned, this is a recent phenomenon. I don't think i have
upgraded any package related to console or screen. Today i upgraded
screen using apt-get to see if the behaviour changes, but it didn't.
Arvind
Reply to: