Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!mimsy!chris From: chris@mimsy.umd.edu (Chris Torek) Newsgroups: comp.unix.questions Subject: POSIX job control, etc Message-ID: <27781@mimsy.umd.edu> Date: 17 Nov 90 16:46:04 GMT References: <14478@smoke.brl.mil> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 14 In article <14478@smoke.brl.mil> gwyn@smoke.brl.mil (Doug Gwyn) writes: >... capsule summary: BSD job control is a horrible kludge that never >did work right Well, that depends on your definition of `work' :-) Seriously, it does its job, but it is insecure and terribly difficult to program. (POSIX job control is also insecure, but only to `denial of service' type attacks---the problem is that user code allocates process group identifiers; this should be done by the system---and is also rather excessively difficult to program. It does otherwise work, mostly.) -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 405 2750) Domain: chris@cs.umd.edu Path: uunet!mimsy!chris