Rogue Processes in Solaris 2.4

I understand that this is something of a widespread problem hence this posting in case it is of use. We experienced rogues being generated when users exited abnormally from their windows telnet or C/S sessions, either by using file/exit, Alt-F4, or CTRL-ALT-DEL. These rogues then spin on the CPU where they get switched off because they have no terminal session then switched back on again seconds later. CPU goes to 100% very fast. If the user exits in this way while printing, the print job can get sent literally thousands of times to the printer. This can drag down the entire printing system if they are small print jobs because Unix runs out of resources to handle them. The problem is due to bugs in the /bin/sh program. These bugs are *not* fixed by published patches to /bin/sh, although they may help in other areas. These rogues can be eliminated 100% by changing all logins to use /bin/ksh instead of /bin/sh. regards -- -- Peter Tashkoff <tashkop@kiwi.co.nz> NZ Kiwifruit Marketing Board Usual Disclaimers Apply Use of this posting by any commercial organisation for the purposes of vilifying another is explicitly prohibited