Subject: Re: run ddb(4) in "batch mode"
To: None <firstname.lastname@example.org>
From: Valeriy E. Ushakov <email@example.com>
Date: 03/28/2007 18:53:11
On Wed, Mar 28, 2007 at 16:00:04 +0200, Jukka Salmi wrote:
> Valeriy E. Ushakov --> current-users (2007-03-28 17:50:36 +0400):
> > On Wed, Mar 28, 2007 at 15:45:02 +0200, Jukka Salmi wrote:
> > > This didn't really work as expected because the ddb.commandonenter
> > > commands caused ddb to print more than ddb.lines (24) lines of output;
> > > thus ddb waited for user input to print the next page of output, and
> > > didn't execute the `reboot' command automatically...
> > >
> > > To fix this problem I added a new variable `batchmode', accessible via
> > > sysctl(3) as the other built-in ddb variables.
> > Uhm. What's wrong with ddb.lines=0 (except that 0 being magic is not
> > documented in ddb(4))?
> Uh, probably nothing, except that it's not documented ;-)
I've documented the meaning of zero for lines (and maxwidth) in ddb(4).
I didn't realize that was not documented until you asked and I
actually looked it up in ddb(4). That behaviour seems kinda natural
b/c e.g. gdb (and probably others) interpret zero height this way too.
It's one of those things you start taking for granted.
Thanks for the heads up.
firstname.lastname@example.org | Zu Grunde kommen
http://snark.ptc.spbu.ru/~uwe/ | Ist zu Grunde gehen