On 9/1/05, Christopher Linn <[EMAIL PROTECTED]> wrote: > On Wed, Aug 31, 2005 at 04:17:06PM -0500, Kevin wrote: > > On 8/31/05, Christopher Linn <[EMAIL PROTECTED]> wrote: > > > > Kevin Kadow wrote: > > > > > only found a couple of X applications (xtacy, xlock) failing on > > > > > signal 11. > > > ^^^^^ > > > oooooooooooo, that's a biggie.. > > > > I can't tell if you were being serious or sarcastic? > > at the risk of posting public reply to private email (i think it's > probably OK in this case...)
It's OK. Glad that you thought twice about it, so many people don't. > quite serious actually. my desktop is an openbsd box, and my office > is adjacent to a semi-public area at a university. i frequently leave > my office for a few minutes at a time up to a few hours. so, yes i > really do depend on it. Coming back to an open terminal that I know I locked was a bit of a shock. Almost makes me wonder if xlock can be trusted. You'd think it'd set a sighandler when going into a mode, and not 'exit' just because one mode subroutine threw an exception. I'll send a diff to add an additional "**WARNING**" section to the man page. KK
