login sessions keep on using CPU power after being logged out.

login sessions keep on using CPU power after being logged out.

Post by Wanne de Kl » Thu, 16 Nov 1995 04:00:00


it seems that since 1.3.35 or 36 login keeps active after I've closed my
terminal application (I don't always correctly log out). Currently there are
two login sessions active which don't connect to a terminal program (netstat)
for more that 12 hours. They're using up to 45% CPU power each :(
If I remember this behaviour started with 1.3.35 or 36 and it hasn't
disappeared with kernels up to 41.

Can anybody reproduce this strange behaviour?
I'm using slack 2.30.


Wanne de Kler.

PS Has the kernel mailing list disappeared ? I used to receive a digest but I
haven't seen it for over three weeks now (I've lost the email address).


1. Keeping Track of my Login/outs?csh script

I would like to alter my ".logout" file in csh to add(CAT) to a file so
that I could
keep track of the hours spent and on which host /sun or sgi etc. Is there
script in csh that could accomplish this?

Any help GREATLY appreciated.

Dave who?
Dave's not here.

D. Christian Ehlers

2. Is there a size limitation when making a tar file?

3. keep login session connected

4. C AIX function call to get EXEC NAME

5. Using 'nohup' w/o keeping session open

6. Samba Remote Access

7. Where is Anonymous FTP user login log kept ?

8. Network/httpd problem

9. login sessions to my host eat >90% CPU time

10. How can I tell whether I am logging in on console inside .login?

11. How to keep log when using ufsdump

12. Linux keeps using HD when I logged off..

13. Error Logging in "3004-312 All available login sessions are in use."