atom feed2 messages in org.freebsd.freebsd-currentvfs.ioopt should still be 0 as default
FromSent OnAttachments
Ollivier RobertMar 1, 1998 1:11 pm 
John S. DysonMar 1, 1998 2:18 pm 
Subject:vfs.ioopt should still be 0 as default
From:Ollivier Robert (robe@keltia.freenix.fr)
Date:Mar 1, 1998 1:11:57 pm
List:org.freebsd.freebsd-current

Sorry John, but the latest VM changes you made seems to break things here... With vfs.ioopt=1 (the new default), actived (part of INN + insync patches) dies pretty fast complaining of active's format.

Actived is reading periodically the active file in a buffer and with ioopt enabled, the read() just read... nothing. Thus the in-memory copy of active is junk and actived dies.

Mar 1 20:40:59 keltia actived[7148]: internal no_space2 "alt.2600..." Mar 1 20:40:59 keltia actived[7148]: cant getgrouplist No such file or
directory

An overeager read optimisation maybe ?

Sources from 1998/03/01 06:11 CTM cvs-cur #4103

With vfs.ioopt=0, everything's fine.

To Unsubscribe: send mail to majo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message