On Wed, Aug 01, 2001 at 11:58:52AM -0700, Dima Dorfman wrote:
> Peter Pentchev <[EMAIL PROTECTED]> writes:
> > Or rather, do not try this while syslogd is running.
> >
> > src/sys/kern/subr_log.c defines the operation of the /dev/klog
> > device, and there is an upper limit on the number of proce
Peter Pentchev <[EMAIL PROTECTED]> writes:
> Or rather, do not try this while syslogd is running.
>
> src/sys/kern/subr_log.c defines the operation of the /dev/klog
> device, and there is an upper limit on the number of processes
> that can simultaneously open the log device - the limit is one.
>
On Mon, Jul 30, 2001 at 02:35:21PM -0700, Kris Kennaway wrote:
> On Mon, Jul 30, 2001 at 11:50:18AM -0700, Hans Zaunere wrote:
> > Hello,
> >
> > I'm looking to access kernel messages directly from
> > the kernel, and not through syslog if I can help it.
>
> Look at how syslogd does it.
Or rath
On Mon, Jul 30, 2001 at 11:50:18AM -0700, Hans Zaunere wrote:
> Hello,
>
> I'm looking to access kernel messages directly from
> the kernel, and not through syslog if I can help it.
Look at how syslogd does it.
Kris
PGP signature
Hello,
I'm looking to access kernel messages directly from
the kernel, and not through syslog if I can help it.
When I try to open("/dev/klog", O_RDONLY); I get the
error "Device busy". How can I open this file? Or
are there any other ways of getting at this data?
When I try to open /dev/lo
5 matches
Mail list logo