[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[altq 1021] Re: re: can't open altq device on NetBSD
From: Kenjiro Cho <email@example.com>
Sent: Thursday, August 30, 2001 9:02 AM
Subject: [altq 1020] Re: re: can't open altq device on NetBSD
> If the error occurs at altq_attach(), you will get a different error
> "altqd: can't open altq device: Device busy" indicates:
> > > It's from tbr_install() in libaltq/qop.c at open(/dev/altq/altq,
> > > The corresponding kernel code is altqopen() in sys/altq/altq_conf.c,
> > > and it always returns 0 for opening /dev/altq/altq (cdev minor 0).
So what you are saying is that the error I am receiving is absolutely
impossible. Well, it's occurring... so it must be possible. What debugging
lines could I possibly add that would help? Can I do thinks like adding some
kind of LOG command into the code inside the altqopen() function?
How about a more specific question... I KNOW I can add a log command of some
sort, so can you tell me (someone who programs, but not in C, in Linux, and
definitely not in the kernel) what the syntax of the log command I should
use is, and what you think are the best places to put it?
I noticed that none of the altq kernel code has a single relevant occurrence
of [Ll][Oo][Gg]ing... does that mean you can't do logging in kernel code, or
that you shouldn't? Would I have to add a reference to syslog.h first?
Thank you for your help.