Hi, when I leave and come back to my computer, I findthat bash has closed. The first few times I thought I just closed it, but today when I went to my internship, I purposely left it open, and the top window, and when I came back, guess what, it was closed.

What in the world is going on here? Is it a hacker, or is there something wrong with bash? Only bash closes, no other windows close. This is really starting to concern me.

GNU bash, version 3.1.17(2)-release (i586-mandriva-linux-gnu)
Copyright (C) 2005 Free Software Foundation, Inc.

Thanks in advance,
diode

Your TMOUT environment variable is probably set to a non-zero value. To check,

echo $TMOUT

From the bash man page:

It is probably set in your ~/.bashrc or ~/.bash_profile or /etc/profile.

Hi, thanks for your input. I checked all three of those files, and it wasn't in any of them, although I did echo $TMOUT, and it said 3600.

How do I get this to be 0?

Thanks again,
otacon

Well, it's probably being set by something called from one of those files. What you can try is setting it yourself in your ~/.bashrc

export TMOUT=0

Ok I tried that in all those files, and sourced them, and for each one, it gave an error message saying bash: TMOUT: readonly variable. I tried this as my regular user and as root.

I manned bash and found mention of a select command buried in there, do you think that's what it is? Though I searched all three of those files for that also, and found nothing. Will it be necessary to pass a parameter to bash on the command line just to have a window that doesn't close? Is this even possible? That sounds so dirty to do it that way, I hope there is a way to correct this.

My linux installation is on a 'high' security level. Previously, it was on a 'standard' security level. Would that play a role in this?

Thanks,
otacon

OK, from the Mandriva documentation, you need to edit '/etc/security/msec/security.conf' and add/set 'set_shell_timeout(0)'.

Ok thanks, I added the line to the file. I restarted. But $TMOUT is still = to 3600. It seems like the line wasn't executed.

I went into Mandriva Control Center and didn't see anything about this under security. I'm stuck on what to do now.

Thanks alot,
otacon

Try:

grep -i -r "shell_timeout" /etc/security/*

See if it's set anywhere else.

Aha, I had an apostrophe ' before set. It's fixed now. Do I have to log out, or restart or is there a way to run this file to set the new environment variable value? Also, after seeing the results of what you just suggested, this is the only file that has this line in it. I went to the F2 console and logged in as a different user, and did echo $TMOUT, and it was still set to 3600.

Thanks alot,
otacon

According to the Mandriva documentation, you should just need to run (as root)

msec

The changes will take effect after that (or on the next reboot).

I restarted, and it still is 3600...

Forgot to mention that I ran it as root, and when I ran it, it executed good, because it didn't display any messages after it ran.

otacon

At this point, I suggest you open a bug report with Mandriva.