On 08/01/2012 06:31 PM, Leonid Isaev wrote:
On Wed, 01 Aug 2012 17:50:45 -0500
David C. Rankin drankina...@suddenlinkmail.com wrote:
The only config change I can see in the apcupsd.conf.pacnew is:
LOCKFILE /var/lock - LOCKFILE /etc/apcupsd
I can't see that causing a segfault, could it?
I
Hey David,
-apologies for not quoting correct on this one-
could you check the date and time settings in the BIOS ?
My guess is that it's something weird in the RTC. To make sure it's best to
check outside of the OS.
I'll admit; it's just a huch.
mvg, Guus
On Thu, Aug 2, 2012 at 3:06 PM, David C. Rankin
drankina...@suddenlinkmail.com wrote:
On 08/01/2012 06:31 PM, Leonid Isaev wrote:
On Wed, 01 Aug 2012 17:50:45 -0500
David C. Rankin drankina...@suddenlinkmail.com wrote:
The only config change I can see in the apcupsd.conf.pacnew is:
Guys,
This is one for you to puzzle over. I've never seen it before. I had an
apcupsd commanded shutdown at Aug 1 13:20:15 (not uncommon - power is
terrible). However, when I restarted the hwclock had magically jumped ahead by
1 full month to Sept. 1. (the box was down for 56 minutes until
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/01/2012 03:42 PM, Leonid Isaev wrote:
snip
Aug 1 13:20:15 providence apcupsd[3477]: apcupsd shutdown succeeded
Aug 1 13:20:15 providence kernel: [171092.364247] apcupsd[3477]: segfault
at 0 ip 0805c706 sp bfcdfff0 error 4 in
On Wed, 01 Aug 2012 17:50:45 -0500
David C. Rankin drankina...@suddenlinkmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/01/2012 03:42 PM, Leonid Isaev wrote:
snip
Aug 1 13:20:15 providence apcupsd[3477]: apcupsd shutdown succeeded
Aug 1 13:20:15 providence
6 matches
Mail list logo