Re: [CentOS] Experience with Centos running off usb-stick(s)

2011-07-22 Thread cooleyr
On Jul 21, 2011 8:27 AM, Dennis Jacobfeuerborn denni...@conversis.de
wrote:

 Hi,
 I'm trying to build a redundant duo of firewalls/routers/gateways and I'm
 thinking about not putting any disks in them and instead using a usb-stick
 raid-1 as storage.
 Has anyone any experience with this?

I simply wouldn't build a system that is dependent on USB for the rootfs
full-time, unless it's very unimportant.  I've seen USB ports get disabled
while in-use plenty of times.  Instead, an ATA to CF or SD adapter can be
had quite inexpensively.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] managing a rack full of centos servers

2011-07-19 Thread cooleyr
On Jul 19, 2011 6:48 PM, Jay Leafey jay.lea...@mindless.com wrote:

 I usually use SSH keys in conjunction with ClusterSSH (
http://clusterssh.sourceforge.net), I have been using the 3.27 version with
good results.  It makes managing batches of servers a bit easier, allowing
the execution of the same command across multiple systems at the same time.

In the same vein, I instead recomend pdsh.  It has a few quirks which
increases the learning curve, but it works very, very well, assuming that's
the level of control you want/need.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] svn check out failed for 'connection refused' reason

2011-07-19 Thread cooleyr
On Jul 19, 2011 11:30 AM, Steve liu lsen@gmail.com wrote:
 e.g.
 svn co svn://svn.mplayerhq.hu/mplayer/trunk mplayer
 svn: Can't connect to host 'svn.mplayerhq.hu': Connection refused

 and this is my iptables status and some info to confirm the DNS and ICMP
connection are ok.

Do an nmap scan on svn.mplayerhq.hu.  Look for svn / subversion in etc
services to see which port you specifically need to have open.  I'd bet your
upstream firewall is blocking the port.  You can try connection to the host
+ port with nc -w2 -v to see if you get connected.  Type some junk and you
should see some error back from the server.
If the network looks good with all of the above, the problem is with your
local svn binary, or its configuration.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[Nut-upsuser] Powercom BNT-800AP

2010-02-04 Thread cooleyr
While fundamentally working, I'm having a few issues with the driver...

The default voltage quads (for every model) are way off...  Showing
~95v when it should be ~117V.  I've changed the 4th/final coefficient
to +5.0, but haven't tested extensively (with fluctuating voltages).

The input/output voltage appears to be swapped _most of the time_.
When doing a battery test, or when unplugged, the input stays steady,
and the _output_ voltage reports a drop to ~15V.  OTOH, when the UPS
is shutdown, the ordering appears correct, as the input stays steady,
and the output shows ~5V.

For the above, the Powercom upsmon software appears to special-case
those ~5/15V results, and on the next update, report it as 0V.  I have
no idea how to even special-case the screwy input/output-swapping
behavior...


./powercom -a ups0 -DDD
Network UPS Tools - PowerCom protocol UPS driver 0.12 (2.4.1-2308)
   0.00 debug level is '3'
   0.001406 Flow control disable
   0.150003 Detected: BNT-other-500AP , 120V
   0.153986 Values of arguments:
   0.154001  manufacturer: 'PowerCom'
   0.154009  model name  : 'BNT-other-500AP'
   0.154015  serial number   : 'Unknown'
   0.154022  line voltage: '120'
   0.154029  type: 'BNT-other'
   0.154036  number of bytes from UPS: '16'
   0.154042  method of flow control  : 'no_flow_control'
   0.154051  validation sequence: '{{8,0},{8,0},{8,0}}'
   0.154059  shutdown arguments: '{{1,30},y}'
   0.154073  frequency calculation coefficients: '{0.000208,0.00}'
   0.154084  load percentage calculation coefficients:
'{1.447400,0.00,0.859400,0.00}'
   0.154101  battery percentage calculation coefficients:
'{5.00,0.326800,-825.00,0.465110,0.00}'
   0.154110  voltage calculation coefficients: '{0.954500,5.00}'
   0.305927 input.frequency   (raw data): [raw: 80]
   0.305966 input.frequency: 60.09
   0.305974 output.frequency   (raw data): [raw: 80]
   0.305987 output.frequency: 60.09
   0.305994 ups.load  (raw data): [raw: 0]
   0.306008 ups.load: 0.0
   0.306015 battery.charge (raw data): [raw: 197]
   0.306027 battery.charge: 100.0
   0.306035 input.voltage (raw data): [raw: 119]
   0.306048 input.voltage: 118.6
   0.306055 output.voltage (raw data): [raw: 26]
   0.306067 output.voltage: 29.8
   0.306079 STATUS: OB TEST
   0.306338 dstate_init: sock /var/state/ups/powercom-ups0 open on fd 5
   0.453868 input.frequency   (raw data): [raw: 80]
   0.453907 input.frequency: 60.09
   0.453914 output.frequency   (raw data): [raw: 80]
   0.453925 output.frequency: 60.09
   0.453931 ups.load  (raw data): [raw: 0]
   0.453944 ups.load: 0.0
   0.453950 battery.charge (raw data): [raw: 195]
   0.453961 battery.charge: 100.0
   0.453968 input.voltage (raw data): [raw: 119]
   0.453979 input.voltage: 118.6
   0.453986 output.voltage (raw data): [raw: 26]
   0.453997 output.voltage: 29.8
   0.454008 STATUS: OB TEST
   1.853474 new connection on fd 6
   2.457023 input.frequency   (raw data): [raw: 80]
   2.457070 input.frequency: 60.09
   2.457077 output.frequency   (raw data): [raw: 80]
   2.457088 output.frequency: 60.09
   2.457095 ups.load  (raw data): [raw: 0]
   2.457108 ups.load: 0.0
   2.457115 battery.charge (raw data): [raw: 191]
   2.457140 battery.charge: 95.0
   2.457147 input.voltage (raw data): [raw: 119]
   2.457159 input.voltage: 118.6
   2.457167 output.voltage (raw data): [raw: 25]
   2.457185 output.voltage: 28.9
   2.457197 STATUS: OB TEST
   4.456188 input.frequency   (raw data): [raw: 80]
   4.456240 input.frequency: 60.09
   4.456248 output.frequency   (raw data): [raw: 80]
   4.456259 output.frequency: 60.09
   4.456266 ups.load  (raw data): [raw: 0]
   4.456279 ups.load: 0.0
   4.456286 battery.charge (raw data): [raw: 193]
   4.456656 battery.charge: 100.0
   4.456673 input.voltage (raw data): [raw: 119]
   4.456686 input.voltage: 118.6
   4.456693 output.voltage (raw data): [raw: 119]
   4.456849 output.voltage: 118.6
   4.456978 STATUS: OL
   6.455365 input.frequency   (raw data): [raw: 80]
   6.455420 input.frequency: 60.09
   6.455428 output.frequency   (raw data): [raw: 80]
   6.455439 output.frequency: 60.09
   6.455445 ups.load  (raw data): [raw: 0]
   6.455458 ups.load: 0.0
   6.455465 battery.charge (raw data): [raw: 193]
   6.455476 battery.charge: 100.0
   6.455483 input.voltage (raw data): [raw: 119]
   6.455494 input.voltage: 118.6
   6.455500 output.voltage (raw data): [raw: 119]
   6.455511 output.voltage: 118.6
   6.455522 STATUS: OL

For anyone wondering, I wouldn't recommend these units to anyone else.
 A 400W dumb/personal UPS from 

[Nut-upsuser] (no subject)

2010-02-02 Thread cooleyr


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


[Nut-upsuser] (no subject)

2010-02-02 Thread cooleyr


___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser


Re: [Nut-upsuser] Compiling NUT static binaries

2009-05-19 Thread cooleyr
On Tue, May 19, 2009 at 2:21 PM, cool...@gmail.com wrote:


 I expect there's some libtool / gcc linking flag I'm ignorant of, or
 neglecting to use, but extensive trial and error has not found it.
 [-Xlinker] -all-static , -without-shared, -static-libtool-libs, etc. have
 not had any effect on the end binary.


Problem solved.

The ./configure script errors-out when LDxxx=-all-static is used,
with/without -Xlinker.   However, there's nothing actually wrong with using
the option on this or other systems... It's merely ./configure
brain-damage.

After running configure without the option, adding the -all-static option to
the LDFLAGS of each individual Makefile (in my case, just
nut-2.4.1/clients/Makefile) works perfectly.

I only hope my hours of neddless suffering helps someone.
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser