The issue is not with PICO but with the fact that an ordinary user
had privilages to gobble ALL the systems resources. You could substitute in
any power hungry app here for the same effect. You wanna be looking at
ulimit, getrlimit, setrlimit, sysconf and so on. There are man pages
applenty with same.
m2c,
steve
-----Original Message-----
From: Lee Howard [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 12, 2000 5:08 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: pico can cripple a system
I had a user ftp up a 100MB+ text file and then try opening it with pico.
Well, it brought the system to its knees, and it went unresponsive for
nearly an hour (128MB RAM, 8GB HDD, AMD K6-2/450) until I executed a
'shutdown -r' (and even that took several minutes to initiate).
Now maybe the user wasn't all that careful, but it seems innocent enough.
How is this not a security issue? Seems to me that pico needs to be a
little more concerned about CPU usage when it opens a file.
Thanks.
Lee Howard
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
