ted server maybe the UPS it's on
> is shot, and it's getting power fluctuations. Or maybe
> it's overheating or it's clogged with dust.
>
> Ted
>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] Behalf O
y, January 12, 2005 10:40 AM
> To: freebsd-questions@freebsd.org
> Subject: 4.9 rebooting
>
>
> I have a remote server which has begun re-booting every few days.
>
> Are there any logs which I can examine that may provide a clue as to
> the reason? Or any logging I can tu
I have a remote server which has begun re-booting every few days.
Are there any logs which I can examine that may provide a clue as to
the reason? Or any logging I can turn "on/up" ? I realize that
during a reboot, logs are seldom "up-to-date", but any clue would
be handy.
This is a remote co-locat
>
> I would suggest that something is wrong. FreeBSD
> generally doesn't boot into single user mode unless it's either
> told to, or has to. The most likely probable cause is a bad HDD*,
> but there may be other possibilities.
>
> What happens after someone does enter the default shell path? Doe
Patrick Fish wrote:
Hi,
I just applied the FreeBSD-SA-04:04.tcp patch onto my 4.9-STABLE box and rebooted.
On more than one occasion FreeBSD boots into single user mode and awaits for someone to enter the default shell path. This becomes a problem since the server is remote - is there a way to n
Hi,
I just applied the FreeBSD-SA-04:04.tcp patch onto my 4.9-STABLE box and rebooted.
On more than one occasion FreeBSD boots into single user mode and awaits for someone
to enter the default shell path. This becomes a problem since the server is remote -
is there a way to not have it boot int
