1/7 Someone needs to figure out how larryl jammed up motdedit - isn't
it supposed to exit if you take too long?
\_ Someone else did this by running motdedit, editing the motd with
vi, saving changes, and then leaving vi running "in case someone
overwrote his changes." I guess a limitation of motdedit is that
you actually need to quit your editor entirely in order for it
to relinquish the lock. I have no idea why the time-out doesn't
work effectively.
\_ the first part is wrong. the person did not use motdedit, but
instead just ran "vi /etc/motd.public". The timeout in motdedit
does work so long as motdedit isn't sent SIGSTOP/TSTP, at least
the way motdedit is right now. --Jon
\_ No, you're wrong. I'm the person. I ran motdedit. -emarkp
\_ That would be me. Since motdedit launches the editor,
backgrounding the editor will background motdedit, and the timeout
doesn't work. My solution: don't use motdedit. Vim warns me if I
try to write a file which has changed anyway, so it's of little
use to me. -emarkp
\_ I believe this bug was fixed. The question is how did larryl
jam it up again, this morning?
\_ or last night, as the case may be:
[soda:~] 14:24 (214)last larryl
larryl ttyDi 216.233.16.78 Thu Jan 8 00:47 - 00:49 (00:01) |