Re: [CentOS] apcupsd

2012-11-06 Thread m . roth
Stephen Harris wrote:
> On Tue, Nov 06, 2012 at 04:56:20PM -0500, m.r...@5-cent.us wrote:
>> Anyone else around using apcupsd? I seem to be seeing a problem, and I'd
>
> Yes
>
>> like someone to check me on it: I edit /etc/apcupsd/apccontrol to
>> replace the value of SHUTDOWN from /sbin/shutdown to /bin/false
>>  (we don't want 3 or 6 servers shutting down over a 2 second or so blip,
>> which it really wants to do).
>
> It wouldn't normally do that, until the battery is almost drained.

I dunno, but it appears to, sometimes. And we have such *wonderful* power
in this building, there's at least one major blip, for a second or two,
every night

>> it, I found that the config file was set to the original code... and I
>
> apccontrol isn't flagged as a config file in the rpm
>
>   ./etc/apcupsd/apccontrol
>   .  c /etc/apcupsd/apcupsd.conf
>   .  c /etc/apcupsd/changeme
>   .  c /etc/apcupsd/commfailure
>   .  c /etc/apcupsd/commok
>   .  c /etc/apcupsd/offbattery
>   .  c /etc/apcupsd/onbattery
>   .  c /etc/logrotate.d/apcupsd
>
>
>> Has anyone seen this behavior?
>
> The script says
>
> # WARNING: the apccontrol file will be overwritten every time you update
> your
> # apcupsd, doing `make install'. Your own customized scripts will _not_ be
> # overwritten. If you wish to make changes to this file (discouraged), you
> # should change apccontrol.sh.in and then rerun the configure process.
>
> If you can't change apcupsd.conf config to meet your needs then _don't_
> change apccontrol; add a custom script that does an "exit 99" to prevent
> the shutdown from running.

It looks like you're right... EXCEPT that you missed the part about
changing apccontrol.sh.in, which appears to me to be something you get if
you build apcusd, rather than just install it via yum. And there's no
other obvious way to deal with not wanting to shut it down if you have
multiple machines, and don't want to ever have it tell everybody to shut
down.

Suggestions on what I can do *other* than build the package myself? I
dunno, the times I see it shut down have *not* shut down for 3 or 5 min,
nor do I think that was the max left runtime.

  mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] apcupsd

2012-11-06 Thread Keith Roberts
On Tue, 6 Nov 2012, m.r...@5-cent.us wrote:

> To: CentOS mailing list 
> From: m.r...@5-cent.us
> Subject: [CentOS] apcupsd
> 
> Anyone else around using apcupsd? I seem to be seeing a problem, and I'd
> like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace
> the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3
> or 6 servers shutting down over a 2 second or so blip, which it really
> wants to do).
>
> What's happened is that a machine shut down the other day, and looking at
> it, I found that the config file was set to the original code... and I
> *KNOW*, for a fact, that I went through every single server that's
> attached to a UPS many months ago, after something important shut down,
> and fixed all of them.
>
> So, it looks like an upgrade undid my change, rather than creating
> apccontrol.rpmnew.

Hi Mark.

I've been using apcupsd for years.

I'm on Centos 5.8.

Don't you mean apcupsd.conf for your configuration settings?

That's the one I use to configure apcupsd.

Keith

---
Websites:
http://www.karsites.net
http://www.php-debuggers.net
http://www.raised-from-the-dead.org.uk

All email addresses are challenge-response protected with
TMDA [http://tmda.net]
---
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] apcupsd

2012-11-06 Thread Stephen Harris
On Tue, Nov 06, 2012 at 05:49:57PM -0500, m.r...@5-cent.us wrote:
> Stephen Harris wrote:

> > # WARNING: the apccontrol file will be overwritten every time you update
> > your
> > # apcupsd, doing `make install'. Your own customized scripts will _not_ be
> > # overwritten. If you wish to make changes to this file (discouraged), you
> > # should change apccontrol.sh.in and then rerun the configure process.
> >
> > If you can't change apcupsd.conf config to meet your needs then _don't_
> > change apccontrol; add a custom script that does an "exit 99" to prevent
> > the shutdown from running.
> 
> It looks like you're right... EXCEPT that you missed the part about
> changing apccontrol.sh.in, which appears to me to be something you get if

No I didn't.  It's not relevant to rpm installs.

> you build apcusd, rather than just install it via yum. And there's no
> other obvious way to deal with not wanting to shut it down if you have
> multiple machines, and don't want to ever have it tell everybody to shut
> down.

Yes there is; create a custom script for the command ($1) that you want
to trap and make it exit 99; then apccontrol will not continue on to
the shutdown part.

Which I said previously.

> Suggestions on what I can do *other* than build the package myself? I

Read what apccontrol does; determine the commands you want to
trap (probably doshutdown, doreboot) and create a script of that name
in /etc/apcupsd/ and make it "exit 99".

FWIW, my UPS trips many times...

eg
Oct  8 10:03:11 myhost apcupsd[9774]: Power failure.
Oct  8 10:03:15 myhost apcupsd[9774]: Power is back. UPS running on mains.
Oct 10 20:57:12 myhost apcupsd[9774]: Power failure.
Oct 10 20:57:14 myhost apcupsd[9774]: Power is back. UPS running on mains.
Oct 11 18:51:35 myhost apcupsd[9774]: Power failure.
Oct 11 18:51:38 myhost apcupsd[9774]: Power is back. UPS running on mains.

You might want to check apcaccess for expected runtime

$ apcaccess | egrep 'STATUS|LOADPCT|BCHARGE|TIMELEFT|MBATTCHG|MINTIMEL'
STATUS   : ONLINE 
LOADPCT  :  24.0 Percent Load Capacity
BCHARGE  : 100.0 Percent
TIMELEFT :  36.1 Minutes
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes

-- 

rgds
Stephen
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Copying a file to a usb stick

2012-11-06 Thread John Doe
From: Twanny Azzopardi 
> output of fdisk:
> Command (m for help): p
>
> Disk /dev/sde: 68.7 GB, 68719476736 bytes
> 255 heads, 63 sectors/track, 8354 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>   Device Boot  Start    End  Blocks  Id  System
> /dev/sde1  1    4177    33551721  83  Linux
> ---
> output of ll
> -rw-r--r-- 1 user user 9230653440 Aug  5 22:47 file.tar

Just in case, you did not partition the whole key... right?

One test would be to try to copy 9 files of 1GB and see at what 
point it fails (if it does)...

When I was making my install usb keys, some of them did not seem to 
like "big" files for some unknown reason... Had to replace the DVD 
iso files with the CD ones.

JD
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] disk device lvm iscsi questions ....

2012-11-06 Thread Götz Reinicke - IT Koordinator
Hi,

I have an iscsistorage which I attached to a new centos 6.3 server. I
added logic volumes as usual, the block devices (sdb & sdc) showed up in
dmesg; I can mount and access the stored files.

Now we did an firmware software update to that storage (while
unmounted/detached from the fileserver) and after reboot of the storage
and reatache the iscsi nodes I do get new devices. (sdd & sde)

The last time I remember a simple vgchange -ay changed all neede
settings so that I can mount and use the volumes as expected.

But this time I do get an IO error like

  /dev/sun7110to_dali_LUN_3/lvol0: read failed after 0 of 4096 at
1610608476160: Eingabe-/Ausgabefehler

but also:

  1 logical volume(s) in volume group "sun7110to_dali_LUN_3" now active

What might be messed up? What can I try do get the storage/filesystems
back online?

Thanks for any sugesstion and regards . Götz


-- 
Götz Reinicke - IT-Koordinator - Filmakademie Baden-Württemberg GmbH

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] CentOS-announce Digest, Vol 93, Issue 3

2012-11-06 Thread centos-announce-request
Send CentOS-announce mailing list submissions to
centos-annou...@centos.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-requ...@centos.org

You can reach the person managing the list at
centos-announce-ow...@centos.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of CentOS-announce digest..."


Today's Topics:

   1. CEBA-2012:1427  CentOS 6 util-linux-ng Update (Johnny Hughes)
   2. CentOS Test Day, Friday Nov 9th 2012 (Karanbir Singh)


--

Message: 1
Date: Mon, 5 Nov 2012 15:41:09 +
From: Johnny Hughes 
Subject: [CentOS-announce] CEBA-2012:1427  CentOS 6 util-linux-ng
Update
To: centos-annou...@centos.org
Message-ID: <20121105154109.ga7...@chakra.karan.org>
Content-Type: text/plain; charset=us-ascii


CentOS Errata and Bugfix Advisory 2012:1427 

Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1427.html

The following updated files have been uploaded and are currently 
syncing to the mirrors: ( sha256sum Filename ) 


i386:
dd7a5fd8bb775e27e343865d7a9110946382b1f49e295ba90ea84331fd7636f3  
libblkid-2.17.2-12.7.el6_3.i686.rpm
b4005a1bc774bd66cc05df7cf364805efc109a28f1829c267e586611a43b5872  
libblkid-devel-2.17.2-12.7.el6_3.i686.rpm
8424b15885f76f63f13aadc33c4c0272ea6d00a95495845fcfc3e3716030e603  
libuuid-2.17.2-12.7.el6_3.i686.rpm
be69f072ff0e0117b91c2935828b256456fdf3418dd518b6191a01abd3e27b66  
libuuid-devel-2.17.2-12.7.el6_3.i686.rpm
877c38619713a86c631d0c2fa1b1d216a502a0df228a05dcd6aaad1bd797102c  
util-linux-ng-2.17.2-12.7.el6_3.i686.rpm
d793420f8c03d1cc98ee797527e3f989151fd4c683d67d71fb57503db20e9fda  
uuidd-2.17.2-12.7.el6_3.i686.rpm

x86_64:
dd7a5fd8bb775e27e343865d7a9110946382b1f49e295ba90ea84331fd7636f3  
libblkid-2.17.2-12.7.el6_3.i686.rpm
c0d1052c15e5a797e5b24096cab075c781aa4403f440fff1537f644384dc4479  
libblkid-2.17.2-12.7.el6_3.x86_64.rpm
b4005a1bc774bd66cc05df7cf364805efc109a28f1829c267e586611a43b5872  
libblkid-devel-2.17.2-12.7.el6_3.i686.rpm
33ce2412f436c434efd3515f135ea546207faa83ec4db162ff7d662dd0cb08d8  
libblkid-devel-2.17.2-12.7.el6_3.x86_64.rpm
8424b15885f76f63f13aadc33c4c0272ea6d00a95495845fcfc3e3716030e603  
libuuid-2.17.2-12.7.el6_3.i686.rpm
3596829dcc1d5f16406e69244c1741232516d336ff43354b2d2c169fae2813d5  
libuuid-2.17.2-12.7.el6_3.x86_64.rpm
be69f072ff0e0117b91c2935828b256456fdf3418dd518b6191a01abd3e27b66  
libuuid-devel-2.17.2-12.7.el6_3.i686.rpm
7b1a7796f8afcf4c2661c2c7c53fd7e16ec271aa63d17953fd36f2e34b1f4bab  
libuuid-devel-2.17.2-12.7.el6_3.x86_64.rpm
877c38619713a86c631d0c2fa1b1d216a502a0df228a05dcd6aaad1bd797102c  
util-linux-ng-2.17.2-12.7.el6_3.i686.rpm
39dda2f005352375f5d12c4064f117d3ef6dbd1b78a5ebe78418e513a144864f  
util-linux-ng-2.17.2-12.7.el6_3.x86_64.rpm
37bac3fd81a48610cf9df51f04ed1c48f0a4679e693ac5ba503a057a801c54ab  
uuidd-2.17.2-12.7.el6_3.x86_64.rpm

Source:
b11e72d9796cb0841aef84af8fb8bbadafd1902592be195254f153582e25635a  
util-linux-ng-2.17.2-12.7.el6_3.src.rpm



-- 
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net



--

Message: 2
Date: Mon, 05 Nov 2012 18:20:19 +
From: Karanbir Singh 
Subject: [CentOS-announce] CentOS Test Day, Friday Nov 9th 2012
To: CentOS Announcements List 
Message-ID: <50980363.4010...@centos.org>
Content-Type: text/plain; charset=ISO-8859-1


Reminder Date: Friday November 9th, 2012
Time: From 5:00 UTC to 23:00 UTC

We would like to invite everyone to come join us in #centos-devel on
irc.freenode.net this Friday Nov 9th, 2012 for a CentOS test day. The
aim of the exercise is to get more people looking at the tests we
already have, running them on their infrastructure and ultimately
joining the effort as contributors.

You will need a machine instance ( either physical machine, or a VPS or
a Cloud Instance or a VM on your machine ); need a VM image ? you can
download one from here as prep :
http://dev.centos.org/centos/test-images/ - being able to connect to the
internet from that machine instance is essential, and as there are quite
a few packages installed / uninstalled / cleaned out - a local CentOS
mirror would be handy if you are on a slow link to the internet.

The tests are mostly written in bash, but you can use any language you
like - just grab yourself a gitorious.org account in advance. Knowledge
of git helps, but isn't necessary.

The test day will run from 05:00 UTC till 23:00 UTC, and there will be a
couple of the CentOS QA guys and people who have contributed to the
tests already, to help you get started and join the effort. We will have
brief, clear instructions on  :
- Getting a copy of the most current tests
- Set them up on your machine instance
- Run the tests
- Feedback results and recommendations
- Templates to wri

Re: [CentOS] Centos 6: Dell GX270 fails to power down (but reboots)

2012-11-06 Thread Rainer Traut
Am 05.11.2012 19:28, schrieb James A. Peltier:
> - Original Message -
> | Hi,
> |
> | am using latest C6 on a Dell GX270 with latest Bios.
> | It fails to power down but restarts when running
> | $ sudo poweroff
> |
> | I tried some google hints for kernel boot option:
> | acpi=force
> | no help, looks like acpi is working anyway when looking in dmesg
> | acpi=off
> | makes e1000 nic fail to initialize
> |
> | Any suggestions?
> | Rainer
>
>
> Update the BIOS.  Should fix it.  We had this issue a while back and the new 
> BIOS corrected the issue.
>

Thx for all your answers, but latest Bios is installed (A07 from year 2006).
The pc is has not crashed so far, except the poweroff thingy so I guess 
hw is ok.
FWIW under C5 all was well.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6: Dell GX270 fails to power down (but reboots)

2012-11-06 Thread Sorin Srbu
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf 
Of Rainer Traut
Sent: den 6 november 2012 13:53
To: centos@centos.org
Subject: Re: [CentOS] Centos 6: Dell GX270 fails to power down (but reboots)

>Thx for all your answers, but latest Bios is installed (A07 from year 2006).
>The pc is has not crashed so far, except the poweroff thingy so I guess
>hw is ok.
>FWIW under C5 all was well.

A wild shot; if you have physical access to the computer, could you please 
open it up and check the capacitors, especially around the cpu?

-- 
/Sorin


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6: Dell GX270 fails to power down (but reboots)

2012-11-06 Thread Rainer Traut
Am 05.11.2012 12:09, schrieb Nux!:
> On 05.11.2012 10:38, Rainer Traut wrote:
>> Hi,
>>
>> am using latest C6 on a Dell GX270 with latest Bios.
>> It fails to power down but restarts when running
>> $ sudo poweroff
>>
>> I tried some google hints for kernel boot option:
>> acpi=force
>> no help, looks like acpi is working anyway when looking in dmesg
>> acpi=off
>> makes e1000 nic fail to initialize
>>
>
> Just stabbing in the dark: do you have acpid installed?
>
Yes, it is installed and running.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6: Dell GX270 fails to power down (but reboots)

2012-11-06 Thread m . roth
Sorin Srbu wrote:
> Behalf
> Of Rainer Traut
>
>>Thx for all your answers, but latest Bios is installed (A07 from year
>> 2006). The pc is has not crashed so far, except the poweroff thingy so
I guess
>>hw is ok. FWIW under C5 all was well.
>
> A wild shot; if you have physical access to the computer, could you please
> open it up and check the capacitors, especially around the cpu?

Here's another one: there's an option in the BIOS of some servers for
"return to previous state" on loss of power. If that's there, you might
try it the other way.

I don't suppose the system's still under warranty

 mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6: Dell GX270 fails to power down (but reboots)

2012-11-06 Thread Rodrigo K. Ferreira
Try e1000e or http://elrepo.org/tiki/kmod-e1000
Em 06/11/2012 12:42,  escreveu:

> Sorin Srbu wrote:
> > Behalf
> > Of Rainer Traut
> >
> >>Thx for all your answers, but latest Bios is installed (A07 from year
> >> 2006). The pc is has not crashed so far, except the poweroff thingy so
> I guess
> >>hw is ok. FWIW under C5 all was well.
> >
> > A wild shot; if you have physical access to the computer, could you
> please
> > open it up and check the capacitors, especially around the cpu?
>
> Here's another one: there's an option in the BIOS of some servers for
> "return to previous state" on loss of power. If that's there, you might
> try it the other way.
>
> I don't suppose the system's still under warranty
>
>  mark
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] tcsh

2012-11-06 Thread Bowie Bailey
On 11/6/2012 9:59 AM, Hossein Lanjanian wrote:
> Hi every body
> for run a software on centos, I must use tcsh shell.
> but when I run the command:
> [root@localhost ~]# tcsh
>   the following message appears:
> Bad : modifier in $ (/).
>
> please help!

Did you try Google?
http://lmgtfy.com/?q=Bad+%3A+modifier+in+%24+(%2F).

Looking at the first few results, it looks like the problem is probably 
a syntax error in one of your startup files where it is trying to set an 
environment variable.  This could be in .cshrc, .tcshrc, .login, or a 
few others (see the tcsh man page) for a list of files read on startup.

-- 
Bowie
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] tcsh

2012-11-06 Thread m . roth
Hossein Lanjanian wrote:
> Hi every body
> for run a software on centos, I must use tcsh shell.
> but when I run the command:
> [root@localhost ~]# tcsh
>  the following message appears:
> Bad : modifier in $ (/).
>
> please help!

Sounds like your ~/.tcshrc has a bug in it.

   mark



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] Centos 6: Dell GX270 fails to power down (but reboots)

2012-11-06 Thread Leon Fauster
Am 06.11.2012 um 13:52 schrieb Rainer Traut:
> Am 05.11.2012 19:28, schrieb James A. Peltier:
>> 
>> Update the BIOS.  Should fix it.  We had this issue a while back and the new 
>> BIOS corrected the issue.
>> 
> 
> Thx for all your answers, but latest Bios is installed (A07 from year 2006). 
> The pc is has not crashed
> so far, except the poweroff thingy so I guess hw is ok. FWIW under C5 all was 
> well.


How much memory is installed?

--
LF


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] disk device lvm iscsi questions ....

2012-11-06 Thread James A. Peltier
- Original Message -
| Hi,
| 
| I have an iscsistorage which I attached to a new centos 6.3 server. I
| added logic volumes as usual, the block devices (sdb & sdc) showed up
| in
| dmesg; I can mount and access the stored files.
| 
| Now we did an firmware software update to that storage (while
| unmounted/detached from the fileserver) and after reboot of the
| storage
| and reatache the iscsi nodes I do get new devices. (sdd & sde)
| 
| The last time I remember a simple vgchange -ay changed all neede
| settings so that I can mount and use the volumes as expected.
| 
| But this time I do get an IO error like
| 
|   /dev/sun7110to_dali_LUN_3/lvol0: read failed after 0 of 4096 at
| 1610608476160: Eingabe-/Ausgabefehler
| 
| but also:
| 
|   1 logical volume(s) in volume group "sun7110to_dali_LUN_3" now
|   active
| 
| What might be messed up? What can I try do get the
| storage/filesystems
| back online?
| 
|   Thanks for any sugesstion and regards . Götz
| 
| 
| --
| Götz Reinicke - IT-Koordinator - Filmakademie Baden-Württemberg GmbH
| 
| 
| ___
| CentOS mailing list
| CentOS@centos.org
| http://lists.centos.org/mailman/listinfo/centos
| 

Sounds like the update may have renamed the old devices to something new.  This 
has happened once to be with a Dell Equallogic firmware update.  Are you 
mounting the devices using a device name or using device labels?  If the former 
you should use labels if you created them or the UUID.  If you have a look in 
/dev/disk you'll see all the options available to your OS.  If you choice to go 
with UUID then have a look in /dev/disk/by-uuid to get the path

-- 
James A. Peltier
Manager, IT Services - Research Computing Group
Simon Fraser University - Burnaby Campus
Phone   : 778-782-6573
Fax : 778-782-3045
E-Mail  : jpelt...@sfu.ca
Website : http://www.sfu.ca/itservices
  http://blogs.sfu.ca/people/jpeltier

"The smartest people are constantly revising their understanding, reconsidering 
a problem they thought they’d already solved. They’re open to new points of 
view, new information, new ideas, contradictions, and challenges to their own 
way of thinking." - Jeff Bezos
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] apcupsd

2012-11-06 Thread m . roth
Anyone else around using apcupsd? I seem to be seeing a problem, and I'd
like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace
the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3
or 6 servers shutting down over a 2 second or so blip, which it really
wants to do).

What's happened is that a machine shut down the other day, and looking at
it, I found that the config file was set to the original code... and I
*KNOW*, for a fact, that I went through every single server that's
attached to a UPS many months ago, after something important shut down,
and fixed all of them.

So, it looks like an upgrade undid my change, rather than creating
apccontrol.rpmnew.

Has anyone seen this behavior?

  mark



___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] apcupsd

2012-11-06 Thread Stephen Harris
On Tue, Nov 06, 2012 at 04:56:20PM -0500, m.r...@5-cent.us wrote:
> Anyone else around using apcupsd? I seem to be seeing a problem, and I'd

Yes

> like someone to check me on it: I edit /etc/apcupsd/apccontrol to replace
> the value of SHUTDOWN from /sbin/shutdown to /bin/false (we don't want 3
> or 6 servers shutting down over a 2 second or so blip, which it really
> wants to do).

It wouldn't normally do that, until the battery is almost drained.

Taken from apcupsd.conf:
  # If during a power failure, the remaining battery percentage
  # (as reported by the UPS) is below or equal to BATTERYLEVEL, 
  # apcupsd will initiate a system shutdown.
  BATTERYLEVEL 5

  # If during a power failure, the remaining runtime in minutes 
  # (as calculated internally by the UPS) is below or equal to MINUTES,
  # apcupsd, will initiate a system shutdown.
  MINUTES 3

Basically, systems shouldn't shutdown with a '2 second blip' unless
your battery is dead.

> it, I found that the config file was set to the original code... and I

apccontrol isn't flagged as a config file in the rpm

  ./etc/apcupsd/apccontrol
  .  c /etc/apcupsd/apcupsd.conf
  .  c /etc/apcupsd/changeme
  .  c /etc/apcupsd/commfailure
  .  c /etc/apcupsd/commok
  .  c /etc/apcupsd/offbattery
  .  c /etc/apcupsd/onbattery
  .  c /etc/logrotate.d/apcupsd
  

> Has anyone seen this behavior?

The script says

# WARNING: the apccontrol file will be overwritten every time you update your
# apcupsd, doing `make install'. Your own customized scripts will _not_ be
# overwritten. If you wish to make changes to this file (discouraged), you
# should change apccontrol.sh.in and then rerun the configure process.

If you can't change apcupsd.conf config to meet your needs then _don't_
change apccontrol; add a custom script that does an "exit 99" to prevent
the shutdown from running.

-- 

rgds
Stephen
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos