Hi again,
Sorry for replying to my own post, I wanted to add some more details.
Here's a more detailed message about the panic on boot:
Mounting root from ufs:/dev/ad0s1a
Pre-seeding PRNG: kickstart.
Loading configuration files.
Entropy harvesting: interrupts ethernet point_to_point kickstart.
Hi,
Another vinum question. I have a machine running 5-CURRENT sources from
yesterday (yes I know the dangers of running CURRENT and I did read the
mailing list archives). I think I found a bug, if I add
start_vinum="YES" to /etc/rc.conf, at boot I get a panic with a message
saying:
panic: v
porting
data?
Thanks
Mario Doria
[EMAIL PROTECTED]
Send spam here -> [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ed on signal 11
pid 17611 (httpd), uid 80: exited on signal 11
On the error log I found this:
[Thu Apr 1 16:52:35 2004] [notice] child pid 17611 exit signal Segmentation
fault (11)
This is after running for 24 hours. Has anybody else experienced something
similar?
Thanks
Hi all,
I was reading a pf ruleset example at
http://www.openbsd.org/faq/pf/example1.html when I noticed this:
(1) pass in on $int_if from $int_if:network to any keep state
(2) pass out on $int_if from any to $int_if:network keep state
(3) pass out on $ext_if proto tcp all modulate state flags