The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: logging boot messages before they vanish...

On Tue, 24 Dec 1996, Craig Sanders wrote:

> On Fri, 20 Dec 1996, Philip Hands wrote:
> 
> > Mail to root wouldn't do me much good though because I always alias
> > `root' to an account on a central machine, which is often not on the
> > same site, and so might not be easily available.
> 
> yes, if it does become widely used, it should be changed to use a
> logfile like /var/log/sysinfo which you suggested (or /var/log/bootlog),
> or allow the user to choose whether it gets logged to a file or mailed
> to root or some other account.

I would also like to have something like that.

> maybe just mail it to debian_sysinfo, and debian_sysinfo can be an alias
> in /etc/aliases which either refers to an email address or a file?

Good idea.

> 
> > Instead, how about putting the info in:
> >
> >   /var/log/sysinfo
> >
> > or somesuch, overwriting it on each boot so it doesn't grow.
> 
> rotate it on boot rather than overwrite. i sometimes find it's useful
> to compare old dmesg mails with the current one. That's the main reason
> i mail it to root, actually - a mail folder with dated subject lines
> seemed the least hassle way of managing my boot history record.

You're right. I would suggest to have a place where one can decide if one
wants to have it mailed or just saved in a log file.

BTW, you said you already do this. What messages are you logging? If you
just call `dmesg' you would only get the kernel messages. But I'm
intrested in logging _all_ messages that go to the console, i.e. all the
"Starting daemon xyz..." and all possible error messages from the scripts.
I have several servers I maintain only via a remote terminal
(rlogin/telnet) so I don't see if a daemon complained upon startup about,
say a missing directory (I had this yesterday). Is there an easy way to do
this?


Thanks,

Chris

--          _,,     Christian Schwarz
           / o \__   schwarz@monet.m.isar.de, schwarz@debian.org,
           !   ___;   schwarz@mathematik.tu-muenchen.de, bm955877@muenchen.org
           \  /        
  \\\______/  !        PGP-fp: 8F 61 EB 6D CF 23 CA D7  34 05 14 5C C8 DC 22 BA
   \          /         http://fatman.mathematik.tu-muenchen.de/~schwarz/
-.-.,---,-,-..---,-,-.,----.-.-
  "DIE ENTE BLEIBT DRAUSSEN!"


--
Please respect the confidentiality of material on the debian-private list.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com