I'd like to know the name of a program that is to u?xterm as autolog is to virtual terminal, i.e. that listens for key-presses, and closes the u?xterm if there are none for just over two hours.� It's annoying me by closing my uxterms in the middle of large (ftp)|(smtp)|(apt) transactions, and I can't stop it running without knowing what it's called. Any suggestions, please?
Dan Hatton dan.hatton@btinternet.com wrote:
and I can't stop it running without knowing what it's called. Any suggestions, please?
Try ps Udan or whatever your username is. You might find that it's running as root, which you should be able to see with ps xf as I assume it's running as a child of xinit or xdm or similar, but then you can't stop it without being root. For non-interactive tasks, you could put them in the batch queue (see man batch) and only do the package configuration interactively, which that auto-killer should be happy about. Running tasks from in screen (see man screen) should also stop the term closing from killing it.
Sorry it's taken me a while to do this. I ran ps Udan and ps Uroot (I think the latter should have picked up anything that would have been in ps xf.) The programs that had texinfo or man pages didn't mention, on searching the documentation for "idle," anything about automatic log-outs. (I picked "idle" because this word features prominently in the warning message I get 127 minutes after the last key-press, and 30 seconds before my uxterm dies.) That leaves as suspects the programs that didn't have texinfo or man pages:
kflushd kupdate kswapd keventd syslogd khubd tserver ptal-mlcd ptal-printd authdaemond.pgsql
Anything ring any bells?
On Thu, 24 Apr 2003, MJ Ray wrote:
Try ps Udan or whatever your username is. You might find that it's running as root, which you should be able to see with ps xf as I assume it's running as a child of xinit or xdm or similar, but then you can't stop it without being root. For non-interactive tasks, you could put them in the batch queue (see man batch) and only do the package configuration interactively, which that auto-killer should be happy about. Running tasks from in screen (see man screen) should also stop the term closing from killing it.
Dan Hatton dan.hatton@btinternet.com wrote:
Sorry it's taken me a while to do this. I ran ps Udan and ps Uroot (I think the latter should have picked up anything that would have been in ps xf.)
Yes, but it won't show the relationships, unless you give it more flags and cross-reference PIDs with PPIDs. I was hoping you'd see some child of xdm or xinit which was doing the mischief.
kflushd kupdate kswapd keventd syslogd khubd tserver ptal-mlcd ptal-printd authdaemond.pgsql
Anything ring any bells?
kflushd kupdated kswapd keventd and khubd are kernel daemons, I think. syslogd writes some of your log files. authdaemond.pgsql sounds like it's part of postgresql. tserver and ptal-* I'm not sure.
On Sat, 10 May 2003, MJ Ray wrote:
Yes, but it won't show the relationships, unless you give it more flags and cross-reference PIDs with PPIDs. I was hoping you'd see some child of xdm or xinit which was doing the mischief.
Ah, right. ps xf run as dan doesn't seem very informative:
PID TTY STAT TIME COMMAND 1302 ? S 0:00 bash /home/dan/.xsession 1345 ? S 0:00 _ /usr/bin/ssh-agent /home/dan/.xsession 1348 ? S 0:00 _ xclock -geometry +1100+0 1349 ? S 0:04 _ tuxeyes -geometry +0+708 1351 ? S 0:01 _ fvwm2 1358 ? S 0:00 _ /usr/lib/fvwm/2.4.6/FvwmPager 7 4 none 0 8 0 1362 ? S 0:00 _ xterm -class UXTerm -title uxterm -u8 1370 pts/1 S 0:00 | _ -csh 1458 pts/1 S 0:00 | _ pine 2392 ? S 0:00 _ xterm -class UXTerm -title uxterm -u8 2393 pts/2 S 0:00 _ -csh 2405 pts/2 R 0:00 _ ps xf
Run as root, it still fails to mention xinit or xdm (or gdm, which seems more plausible on my system:)
2439 pts/2 S 0:00 bash 2442 pts/2 R 0:00 _ ps xf 1 ? S 0:05 init 2 ? SW 0:00 [kflushd] 3 ? SW 0:00 [kupdate] 4 ? SW 0:00 [kswapd] 5 ? SW 0:00 [keventd] 39 ? S 0:04 /sbin/syslogd 42 ? S 0:00 /sbin/klogd 89 ? SW 0:00 [khubd] 165 ? S 0:00 /usr/bin/cWnn4/tserver chuid cwnn 169 ? S 0:00 /usr/sbin/gpm -m /dev/psaux -t imps2 -Rms3 174 ? S 0:00 /usr/sbin/lpd 206 ? S 0:00 /usr/sbin/sleepd 515 ? S 0:00 /usr/sbin/cron 519 ? S 0:00 /usr/sbin/apache 578 ? S 0:00 /usr/lib/laptop-net/ifd /usr/share/laptop-net/link-ch 606 ? S 0:00 ptal-mlcd par:0 -device /dev/lp0 608 ? S 0:00 ptal-printd mlc:par:0 -like /dev/lp0 616 ? S 0:00 /usr/sbin/nscd 617 ? S 0:00 _ /usr/sbin/nscd 618 ? S 0:00 _ /usr/sbin/nscd 619 ? S 0:00 _ /usr/sbin/nscd 620 ? S 0:00 _ /usr/sbin/nscd 621 ? S 0:00 _ /usr/sbin/nscd 622 ? S 0:00 _ /usr/sbin/nscd 654 ? S 0:00 /usr/sbin/automount /var/autofs/misc file /etc/auto.m 662 ? S 0:00 /usr/sbin/automount /var/autofs/net program /etc/auto 680 ? S 0:00 /usr/lib/courier/authlib/authdaemond.pgsql start 682 ? S 0:00 _ /usr/lib/courier/authlib/authdaemond.pgsql start 683 ? S 0:00 _ /usr/lib/courier/authlib/authdaemond.pgsql start 684 ? S 0:00 _ /usr/lib/courier/authlib/authdaemond.pgsql start 685 ? S 0:00 _ /usr/lib/courier/authlib/authdaemond.pgsql start 686 ? S 0:00 _ /usr/lib/courier/authlib/authdaemond.pgsql start 719 ? SN 0:00 /usr/bin/gwd -hd/etc/geneweb -dd/usr/share/doc/genewe 746 ? S 0:00 /usr/sbin/bosserver 750 ? S 0:00 /usr/sbin/rinetd 762 ? S< 1:19 [swapd] 774 ? S 0:02 /usr/bin/X11/xfs -daemon 783 ? S 0:00 /usr/X11R6/bin/xfstt --port 7101 --daemon --user nobo 857 tty8 S 0:00 run --restart --robust /var/lib/console-log/8-_-_var_ 865 tty8 S 0:00 _ less +F /var/log/exim/mainlog 867 tty9 S 0:00 run --restart --robust /var/lib/console-log/9-_-_var_ 869 tty9 S 0:13 _ less +F /var/log/syslog 874 tty1 S 0:00 /sbin/getty 38400 tty1 875 ? S 0:00 /usr/X11R6/bin/Login.app 876 ? S< 0:16 _ /usr/X11R6/bin/X 1455 ttyS1 S 0:00 pppd call bto
Dan Hatton dan.hatton@btinternet.com wrote:
Run as root, it still fails to mention xinit or xdm (or gdm, which seems more plausible on my system:)
[...]
875 ? S 0:00 /usr/X11R6/bin/Login.app 876 ? S< 0:16 _ /usr/X11R6/bin/X
That's because you're using Login.app (the pretty windowmaker-like thing, I believe) instead. Well, I'm stumped by this. After checking the csh and xterm config files, I'd probably give up and start grep -r ing /etc for words like idle, logout and so on.