Re: [Cooker] bash: TMOUT: readonly variable

2002-02-18 Thread Murray J. Root


 Alexander Skwar <[EMAIL PROTECTED]> wrote:
> »Murray J. Root« sagte am 2002-02-17 um 08:11:52 -0500 :
> > Every time I open a term I see:
> >bash: TMOUT: readonly variable
> > at the top, then I get the prompt.
> 
> For me, thgis happened in multi-gnome-terminal when I enabeld the
> checkbox "Use login shell as default" (or somesuch).  In the default
> (with a "normal" shell) I did not get that error message.
> 

It comes from /etc/profile.d/msec.sh
I don't know what it's there for, though, since the person who wrote
the script didn't think to include an explanation.
I deleted the part that sets it readonly, but I don't recommend doing
that till someone explains why it's there in the first place.

-- 
Murray J. Root
[EMAIL PROTECTED] - email
(404) 978-1262 x2646 - voicemail/fax




__
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com





Re: [Cooker] bash: TMOUT: readonly variable

2002-02-18 Thread Alexander Skwar

»Murray J. Root« sagte am 2002-02-17 um 08:11:52 -0500 :
> Every time I open a term I see:
>bash: TMOUT: readonly variable
> at the top, then I get the prompt.

For me, thgis happened in multi-gnome-terminal when I enabeld the
checkbox "Use login shell as default" (or somesuch).  In the default
(with a "normal" shell) I did not get that error message.

Alexander Skwar
-- 
How to quote:   http://learn.to/quote (german) http://quote.6x.to (english)
Homepage:   http://www.iso-top.de  | Jabber: [EMAIL PROTECTED]
   iso-top.de - Die günstige Art an Linux Distributionen zu kommen
   Uptime: 5 days 2 hours 41 minutes




Re: [Cooker] bash: TMOUT: readonly variable

2002-02-18 Thread Claudio

On Monday 18 February 2002 06:26 am, Murray J. Root wrote:
>  Quel Qun <[EMAIL PROTECTED]> wrote:
> > On Sun, 2002-02-17 at 09:40, Claudio wrote:
> > > Il 14:11, domenica 17 febbraio 2002, Murray J. Root ha scritto:
> > > > Every time I open a term I see:
> > > >bash: TMOUT: readonly variable
> > > > at the top, then I get the prompt.
> > >
> > > It's only 2 months that I report this bug...  :-/
> > > C.
> >
> > Hi,
> > Is it 'a' terminal or does it only happen with Eterm?
> > That seems to be the case for me. No such message with gnome-terminal
> > or
> > xterm.
>
> Didn't think to check that before. It's only Eterm.

It happens when sourcing /etc/bashrc here.

-- 
Claudio Panichi
System/Network Admin at Dept. of Physics
"Tor Vergata" University and INFN - Sec. "Roma II"
Remote System is: LINUX Mandrake




Re: [Cooker] bash: TMOUT: readonly variable

2002-02-17 Thread Murray J. Root


 Quel Qun <[EMAIL PROTECTED]> wrote:
> On Sun, 2002-02-17 at 09:40, Claudio wrote:
> > Il 14:11, domenica 17 febbraio 2002, Murray J. Root ha scritto:
> > > Every time I open a term I see:
> > >bash: TMOUT: readonly variable
> > > at the top, then I get the prompt.
> > 
> > It's only 2 months that I report this bug...  :-/
> > C.
> > 
> Hi,
> Is it 'a' terminal or does it only happen with Eterm?
> That seems to be the case for me. No such message with gnome-terminal
> or
> xterm.
> =-=
> kk1
> 
> 

Didn't think to check that before. It's only Eterm.

-- 
Murray J. Root
[EMAIL PROTECTED] - email
(404) 978-1262 x2646 - voicemail/fax




__
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com





Re: [Cooker] bash: TMOUT: readonly variable

2002-02-17 Thread Quel Qun

On Sun, 2002-02-17 at 09:40, Claudio wrote:
> Il 14:11, domenica 17 febbraio 2002, Murray J. Root ha scritto:
> > Every time I open a term I see:
> >bash: TMOUT: readonly variable
> > at the top, then I get the prompt.
> 
> It's only 2 months that I report this bug...  :-/
> C.
> 
Hi,
Is it 'a' terminal or does it only happen with Eterm?
That seems to be the case for me. No such message with gnome-terminal or
xterm.
=-=
kk1





RE: [Cooker] bash: TMOUT: readonly variable

2002-02-17 Thread Murray J. Root

 "Sam Stern" <[EMAIL PROTECTED]> wrote:
> > 
> > Every time I open a term I see:
> >bash: TMOUT: readonly variable
> > at the top, then I get the prompt.
> 
> Hi Murry,
> 
> Did you add "export TMOUT=0" to your .bashrc  in effort to override
> the
> defaults set in msec? When I did I got the error you are reporting.
> That
> variable is set when /etc/sysconfig/msec is imported into the main
> system profile. However, altering that file will NOT stop the default
> auto-logout behavior -- msec will regenerate /etc/sysconfig/msec. You
> need to change the actual msec script by using an override value in
> /etc/security/msec/level.local. So create a file
> /etc/security/msec/level.local that contains:
> 
>  msec.set_shell_variable('TMOUT', 0)  <-- this is the wrong syntax,
> btw.
> I am still trying to locate the right syntax.
> 
> 

 
Nope - no export of TMOUT

-- 
Murray J. Root
[EMAIL PROTECTED] - email
(404) 978-1262 x2646 - voicemail/fax





__
FREE voicemail, email, and fax...all in one place.
Sign Up Now! http://www.onebox.com





RE: [Cooker] bash: TMOUT: readonly variable

2002-02-17 Thread Sam Stern

> 
> Every time I open a term I see:
>bash: TMOUT: readonly variable
> at the top, then I get the prompt.

Hi Murry,

Did you add "export TMOUT=0" to your .bashrc  in effort to override the
defaults set in msec? When I did I got the error you are reporting. That
variable is set when /etc/sysconfig/msec is imported into the main
system profile. However, altering that file will NOT stop the default
auto-logout behavior -- msec will regenerate /etc/sysconfig/msec. You
need to change the actual msec script by using an override value in
/etc/security/msec/level.local. So create a file
/etc/security/msec/level.local that contains:

 msec.set_shell_variable('TMOUT', 0)  <-- this is the wrong syntax, btw.
I am still trying to locate the right syntax.


HTH,


Sam Stern
Bethesda, Md, USA





Re: [Cooker] bash: TMOUT: readonly variable

2002-02-17 Thread Claudio

Il 14:11, domenica 17 febbraio 2002, Murray J. Root ha scritto:
> Every time I open a term I see:
>bash: TMOUT: readonly variable
> at the top, then I get the prompt.

It's only 2 months that I report this bug...  :-/
C.