On Sun, Aug 03, 2003 at 02:36:52PM +0100, Bob Ham wrote:
> On Sun, 2003-08-03 at 09:17, Marcus Brinkmann wrote:
> > On Fri, Aug 01, 2003 at 03:44:17PM +0100, Bob Ham wrote:
> > > dmesgd sits on /dev/klog and stores up its output. it also listens
> > > to an AF_UNIX socket, /tmp/dmesg-socket. dmesg
On Sun, 2003-08-03 at 09:17, Marcus Brinkmann wrote:
> On Fri, Aug 01, 2003 at 03:44:17PM +0100, Bob Ham wrote:
> > dmesgd sits on /dev/klog and stores up its output. it also listens
> > to an AF_UNIX socket, /tmp/dmesg-socket. dmesg clients connect to
> > this and read the stored up klog output t
On Fri, Aug 01, 2003 at 03:44:17PM +0100, Bob Ham wrote:
> dmesgd sits on /dev/klog and stores up its output. it also listens
> to an AF_UNIX socket, /tmp/dmesg-socket. dmesg clients connect to
> this and read the stored up klog output that the server sends them.
How is that any better than syslo
Hi all,
From the readme:
dmesgd sits on /dev/klog and stores up its output. it also listens
to an AF_UNIX socket, /tmp/dmesg-socket. dmesg clients connect to
this and read the stored up klog output that the server sends them.
just put dmesgd in your /libexec/rc and you're away
http://hyacint
On Fri, Aug 01, 2003 at 05:32:26PM +, Robert Millan wrote:
> > No, it's not hurdish, yes, it works around bugs, but does have these
> > wicked features: It Works (tm) and It Exists (tm) :)
>
> Nice! could you add it into GNU sysutils? (at least temporarily)
Definitely not. I can elaborate l
On Fri, Aug 01, 2003 at 03:44:17PM +0100, Bob Ham wrote:
> From the readme:
>
> dmesgd sits on /dev/klog and stores up its output. it also listens
> to an AF_UNIX socket, /tmp/dmesg-socket. dmesg clients connect to
> this and read the stored up klog output that the server sends them.
>
> just p
