🚀 go-pugleaf

The "wakeup" program should make sure it exits after the Emacs that
started it exits.  Otherwise it is possible for it to stay alive and
continue writing "Wake up!" to the pty which might become owned by some
random user.  Another possibility is to always start wakeup with
process-connection-type nil so that it uses a pipe.

-- 
Joe Wells <jbw@uswest.com>

------- Start of forwarded message -------
From: mjassels@concour.cs.concordia.ca
To: Joe Wells <jbw@maverick.uswest.COM>
Subject: Re: Wake up! showing up on users' terminals 
Date: Tue, 30 Jul 91 14:46:19 -0400

You wrote (in response to my question):
>You need to figure out why the "wakeup" program isn't dying when the Emacs
>process that started it exits.  It might be useful to put a check into
>"wakeup" to make it exit after its parent has exited (ie., getppid() == 1).
>
>-- 
>Enjoy,

I never managed to find out exactly why Emacs left "wakeup" alive, but
changing wakeup to test whether getppid() == 1 solved the problem.

Thanks,

Michael Assels
------- End of forwarded message -------