And is the reason why UNIX came up with the idea of individual user
quotas on resources. I'll get some nimrod filled up something like
/tmp with a run away, over night, background process. Waking up a
sysadmin with this sort of "problem" tends to make us just a tad upset
("where is the sob? I'll hang him out the window as a warning!"). I
get very upset at some of our programmers who put on debugging
information with DISPLAY UPON SYSOUT. And then never remove it. So we
end up having the SYSPRINT go to DD DUMMY. Or, worse, out to an
automatically purged SYSOUT class. The worst was when somebody sent it
out the the class which is sent to our reporting system and it swamped
the Windows server and disk space. They got a talking to.On Mon, May 20, 2013 at 11:42 AM, Ted MacNEIL <eamacn...@yahoo.ca> wrote: >>Windows make work until the disk is full. And that is what we want! > > I don't think so. > Windows, in general, is a dedicated single user system. This philosophy is > fine in that environment. > > But, in a shared system, you are NOT the only one affected by full disks! > > - > Ted MacNEIL > eamacn...@yahoo.ca > Twitter: @TedMacNEIL > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
