🚀 go-pugleaf

That program I posted a while ago that forks a process and crashes when that
process finishes -- well, I got it working. Turns out I was doing something
that seems legal, but causes a crash much later.

But I have another problem now: After the child process dies, the main program
reads from Standard Input, and I get a [1] + Stopped (tty input)

There are two reasons why this should not occur:

1. It's running in the foreground. Why stop a foreground process because it
   wants to read from Stamdard in?
2. Standard input under normal circumstances (I run it from the console to
   debug but it's supposed to run off the modem port) is the modem port. Hey!
   I'd like to read from the modem port, please!

Something weird: the child process itself runs a child process: gsh, and resumeswhen gsh quits. If I remove the code to run gsh (thus making the program pretty
useless, but still :)) it never mentions [1] + Stopped (tty input)

Because of this, it seems as though gsh somehow changes the environment of its
parent process. Under no circumstances should a child be able to do that!

Jawaid, you suggested creating a new process group, but (1) I don't see how thatwould help, and (2) How would that be done anyway?

__                __          _          __
|_) |_| | |  |  | |_)   |  | /_\ |\ | |\ |_) \_/  % NetMail:          %
|   | | | |_ |_ | |      \/  | | | \| |/ |\   |   %   Vandry@Cam.Org  %