if anyone else is using the myricom ethernet driver,
could you contact me off list?
- erik
On Jun 21, 2009, at 7:11 AM, erik quanstrom wrote:
On Sun Jun 21 07:59:52 EDT 2009, 9f...@hamnavoe.com wrote:
Forgot to add that I've only seen one error on the console during
all of this:
/boot/fossil: could not write super block; waiting 10 seconds
/boot/fossil: blistAlloc: called on clean
On Sun Jun 21 07:59:52 EDT 2009, 9f...@hamnavoe.com wrote:
> > Forgot to add that I've only seen one error on the console during all of
> > this:
> > /boot/fossil: could not write super block; waiting 10 seconds
> > /boot/fossil: blistAlloc: called on clean block.
>
> I get a few of these nearly
> but "ls -l /mail/ratify > debug.log" gives me nothing. It looks like
> upas/smtpd cannot access /mail/ratify. How do I get ratfs to work?
since smtpd runs as none if you're starting it from listen in
the typical way, i was going to suggest that a process running
as none might not have sufficient
Moin,
I try to get ratfs to work. I've created a mountpoint under /mail,
run ratfs from cpurc and add "mount -c #s/ratify /mail/ratify" to
/lib/namespace.
Then I add a IP address to /mail/lib/blocked and reload the config
with "echo reload > /mail/ratify/ctl". I can see the file under
/mail/ratif
> /boot/fossil: could not write super block; waiting 10 seconds
> /boot/fossil: blistAlloc: called on clean block.
I have a few a day for the last 5 years on my home server, and one a week
on the work machine... I always ignored them.
-Steve
> Forgot to add that I've only seen one error on the console during all of this:
> /boot/fossil: could not write super block; waiting 10 seconds
> /boot/fossil: blistAlloc: called on clean block.
I get a few of these nearly every day. I've been assuming they are benign.
