On Wed, 25 Sep 2002, Mikhail Teterin wrote:
:
Attempts to shutdown gracefully result in panic -- negative refcount in
vnrele (vfrele?) in vnclose() called from vnclosefile() -- can not be
more precise without the serial console and another machine.
Same here. cvsup'd this afternoon.
sc
Hi! I'm experiencing an increasing amount of problems here, and will
try to list them below. Some of this may be well known already, but,
hopefully, something will be usefull.
Unless I set rc_ng to NO, the ypbind will not start, even though
enable_nis_client is set and Starting ypbind is
I thought it was just me, but since last week sometime I have been seeing
several strange crashes in X. It usually has something to do with the
keyboard. X will bomb out saying it caught a sig11, and the message in my
system log shows a sig6.
At first I thought this was due to using XFree that I
Mikhail Teterin wrote:
Unless I set rc_ng to NO, the ypbind will not start, even though
enable_nis_client is set and Starting ypbind is displayed on boot.
Do you have rpcbind_enable set? ypbind needs the portmapper and will
silently exit if it isn't running.
Lars
--
Lars Eggert [EMAIL
In the last episode (Sep 25), Lars Eggert said:
Mikhail Teterin wrote:
Unless I set rc_ng to NO, the ypbind will not start, even though
enable_nis_client is set and Starting ypbind is displayed on boot.
Do you have rpcbind_enable set? ypbind needs the portmapper and will
silently exit if
On Wed, 25 Sep 2002, Mikhail Teterin wrote:
Hi! I'm experiencing an increasing amount of problems here, and will try
to list them below. Some of this may be well known already, but,
hopefully, something will be usefull.
Unless I set rc_ng to NO, the ypbind will not start, even though
Dan Nelson wrote:
Ooh. bug! rc.d/ypbind should have the same check all the other
rpcbind-dependant scripts have:
ypserv_precmd() { case ${OSTYPE} in FreeBSD) if ! checkyesno
rpcbind_enable \ ! /etc/rc.d/rpcbind forcestatus 1/dev/null 21
then force_depend rpcbind || return 1 fi
On Wed, 25 Sep 2002, Mikhail Teterin wrote:
[...]
Unless I set rc_ng to NO, the ypbind will not start, even though
enable_nis_client is set and Starting ypbind is displayed on boot.
Locally, I discovered that the hard dependency of ypbind on rpcbind
now seems to be broken. Try setting
On Wed, 25 Sep 2002, Mikhail Teterin wrote:
Thanks, but I have much bigger troubles at the moment :-( The workaround
for this one is simple -- rc_ng=NO...
FWIW, this -- introducing this sort of instability just two months
before the scheduled release -- is a lot more damaging than the
On Wed, 25 Sep 2002, Mikhail Teterin wrote:
FWIW, this -- introducing this sort of instability just two months
before the scheduled release -- is a lot more damaging than the
stupid trolls, IMO. The finger-breakers should consider leaving the
troll alone and switching to super-gluing
On Wed, 25 Sep 2002, Mikhail Teterin wrote:
There are probably going to be a few nits involved in the VFS changes,
but there are a number of serious bugs being fixed here. I've been
running into a bug on some boxes involving a race condition that
occurs when newsyslog runs on a busy
11 matches
Mail list logo
