On Sun, 27 Jun 2004, Vladimir Zhurov wrote:
> Hello,
>
> Today's /var/log/messages and /var/log/dmesg.today got filled with:
>
> dmesg.today:
> dscheck(#ar/2): negative b_blkno -1721888480
>
> messages:
> /kernel: dscheck(#ar/2): negative b_blkno -1721888480
I've seen this if the array or partiti
On Jun 28, 2004, at 11:06, Matt Douhan wrote:
why ?
they may not be public machines at all and be isolated to an
environment where
security is not the primary concern
Have you not seen the SSH exploit in "The Matrix Reload"?!?! :> How do
you know some evil-doer wouldn't use an exploit from an int
On Sun, Jun 27, 2004 at 04:59:35PM -0500, Phillip Salzman wrote:
> Hello,
>
> I'm running a Dell 2650 2x3.2Ghz box with HTT disabled (the sysctl variable
> hasn't been set, so the user procs aren't taking advantage of the logical
> CPUs) & am seeing some rather strange issues with stdout processes
On Jun 23, 2004, at 9:30 AM, Richard Beyer wrote:
Don't know who to report this to, the netmask in /etc/snmpd.conf for
ucd-snmp doesn't work as expected.
a.b.c.d/27 reported an error, had to resort to
what was the value of "d" and what was the exact error message? and
what version of snmpd?
_
* Roger Raymond <[EMAIL PROTECTED]> [040628 18:58]:
Hello Roger,
> I have the latest apache2 port installed and I can start the server by
> manually issuing an 'apachectl startssl' command. I have added the
> apache2ssl_enable="YES" to my /etc/rc.conf file, yet on a server reboot
> the apache
On Monday 28 June 2004 18:44, Oliver Fromme wrote:
> A machine with 1.5 years of uptime -- be it in an isolated
> environment or not -- has accumulated the bugs of 1.5 years
> that have been fixed in the latest version of the OS, so to
> speak.
But it has not accumulated the 1.5 years worth of ne
Hello,
> When I run a tail -f on my maillog (fairly active) I'm getting this
> intermittently:
> tail: stdout: Unknown error: 0
> Has anyone else seen this recently or have any recommendations?
Yes, sometimes...
But I can not find conditions when it happens
_
Hi,
By accident I happen to come across this remarkable limit of
uptime registration for FreeBSD systems. After 497 days, the
timer jumps to zero again.
497 days is less than a 1.5 years !
Has this been fixed in newer versions of FreeBSD (stable and/or
current) ? Or is there a hardware limitation (
Hello,
I'm running a Dell 2650 2x3.2Ghz box with HTT disabled (the sysctl variable
hasn't been set, so the user procs aren't taking advantage of the logical
CPUs) & am seeing some rather strange issues with stdout processes.
When I run a tail -f on my maillog (fairly active) I'm getting this
in
