Re: DEITY TEAM -- REQUEST FOR FUNCTIONALITY and COMMENTS
I <LeBlanc@mcc.ac.uk> wrote:
> (a) It would be nice to have some sort of temporary audit trail
> for dselect.
"Karl M. Hegbloom" <firstname.lastname@example.org> wrote:
> If errors are always reported on stderr, perhaps it can be tee'd into
> a log file... That's how it's done, right?
What I meant was this: it is apparently possible to make a series of
selections from dselect and screw up the system. It would be nice to
know how things got messed up. The stderr messages only report on
the current state; they don't explain how you got there. I want a
log of all selections, deselections, etc, after starting dselect.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .