Darned clock watchers!

[Kenneth Brody]

Quoting Fairlight (Fri, 12 Dec 2008 00:21:39 -0500):
[...]
> The only problem is that it gets suspended for tty output if it's
> backgrounded.  To work, it has to be the foreground process--which it
> wouldn't be if you wanted to -do- anything with the terminal session.
>
> Now, I -know- for a fact that sysinfo didn't have this issue.  I know this
> for certain because I personally used it for over three years, so I'm 100%
> positive that it didn't have concurrency issues.
[...]

Define "backgrounded".

What if it simply fork()ed itself and had the parent exit()?  What would
cause the child's output to be blocked?

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com