similar to: repeater problem

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this

Dear Arnaud, Now I started to write a driver that simulates continous power breaks. (E.g. in every 30 minutes.) This could be used for testing of setup of client upsmons. I have to simulate a behaviour of a real UPS. The physical model contains an extra attribute: the charging current that needed to compute recharge time and actual battery charge during the recharge process. Can we call this

What is the sign of battery.current value? I wonder if the negative number means charging or discharging. Gabor

Dear folks, The patch in attachment allows upssched to put actual UPS name into command line even if configuration contains wildcard (*). E.g. AT LOWBATT * EXECUTE "LOWBATT %s" AT ONLINE ups3 EXECUTE "ONLINE %s" where %s is replaced with UPS name before logging and execution. A possible further enhancement could be if regular expressions are also acceptable in place of

Dear folks, I'm thinking about writing a multithreaded driver. I wonder if library routines (like dstate_*) are thread-safe? Regards Gabor

I wonder if ups.status: OB LB OFF is valid? Or OB and OFF are mutually exclusive flags? Regards Gabor

Dear folks, strace shows that snmp-ups driver writes to stderr: [pid 21825] write(2, "No log handling enabled - turnin"..., 52) = 52 | 00000 4e 6f 20 6c 6f 67 20 68 61 6e 64 6c 69 6e 67 20 No log h andling | | 00010 65 6e 61 62 6c 65 64 20 2d 20 74 75 72 6e 69 6e enabled - turnin | | 00020 67 20 6f 6e 20 73 74 64 65 72 72 20 6c 6f 67 67 g on std err logg | | 00030 69 6e

Dear folks, According to mge-mib.c (NUT 2.6.2) LB condition is gained from variable .1.3.6.1.4.1.705.1.5.14.0 (i.e. upsmgBatteryLowBattery.0). The test device of me does not set this variable to yes(1) even if runtime drops below the preconfigured limit. I complained about this at Schneider Electric. They replied that low battery status is indicated by .1.3.6.1.4.1.705.1.5.14.0

Dear folks, I had to rewrite UPS::Nut because it was not developed since 2002 and it was based a very old version of upsd speaking a totally outdated protocol. If some of you interested in it you can get from my debian repository. package name is libups-nut-perl. Add this to your APT sources: deb http://debian6.ki.iif.hu/ lenny contrib deb-src http://debian6.ki.iif.hu/ lenny contrib Or simply

reassign 609649 logcheck-database thanks Hi On Wed, Jan 12, 2011 at 05:40:35PM +0100, Kiss Gabor (Bitman) wrote: > > Thanks for the suggestion, but are you sure that this is actually > > part of cron-apt? I can not find any logcheck rules in the cron-apt > > sources. > > Ooops! You are right, I missed the addressee. :-) > File /etc/logcheck/ignore.d.server/cron-apt

Hi, I have a NUT client that requires the UPS it monitors to be named "ups". The client (a Synology NAS) does not provide a method to change this configuration. My setup consists of multiple UPSes monitored by a single master and I'd rather not have 1/4 UPSes named `ups` while the other 3/4 are named something descriptive and helpful for administration. I think I should be able

On Jan 1, 2015, at 8:23 PM, Charles Lepple <clepple at gmail.com> wrote: > On Jan 1, 2015, at 4:57 PM, Jonathan Gammell <jon.gammell at utoronto.ca> wrote: > >> [ups] >> driver = dummy-ups >> port = eaton1 >> desc = "Dummy UPS" > > There is a typo in the specification of "port =" in the dummy-ups man page,

On Jan 1, 2015, at 4:57 PM, Jonathan Gammell <jon.gammell at utoronto.ca> wrote: > [ups] > driver = dummy-ups > port = eaton1 > desc = "Dummy UPS" There is a typo in the specification of "port =" in the dummy-ups man page, but your configuration file is effectively looking for a simulation file named 'eaton1'. The presence of

On 15-01-01 08:57 PM, Charles Lepple wrote: > On Jan 1, 2015, at 8:23 PM, Charles Lepple <clepple at gmail.com> wrote: > >> On Jan 1, 2015, at 4:57 PM, Jonathan Gammell <jon.gammell at utoronto.ca> wrote: >> >>> [ups] >>> driver = dummy-ups >>> port = eaton1 >>> desc = "Dummy UPS" >> >>

https://bugzilla.netfilter.org/show_bug.cgi?id=1220 Bug ID: 1220 Summary: Reverse path filtering using "fib" needs better documentation Product: nftables Version: unspecified Hardware: All OS: All Status: NEW Severity: minor Priority: P5 Component: nft

Hello, I'm trying to setup a UPS configuration whereas I have one physical UPS but two UPS entities loaded by the system used by different network slaves. In my ups.conf configuration I have ... [ups] driver = apcsmart port = /dev/ttyS0 desc = "APC UPS" [qnapups] driver = dummy-ups port = ups at localhost desc = "APC UPS for

Hi list, after upgrading our ldap server, the Domain Admins group doesn't work anymore. Members of the domain admins group don't have any special rights on the workstations (for example, they cannot even change the date of a machine in the domain anymore). When I lookup the group members I get:

I've set up my Samba PDC to act as a WINS server, because I need remote access to it (through a VPN connection). I put "wins support = Yes" into the smb.conf file. As far as I know, WINS doesn't use a unique port number, so enabling the usual NetBIOS ports (137/udp, 138/udp, 139/tcp) on the firewall should be enough to make WINS work. I did this already. I tried to connect to a

Hi all, I''m trying to set up a computer with 2 routes to the internet, much as described at http://lartc.org/howto/lartc.rpdb.multiple-links.html .One of my interfaces (eth5, 192.168.2.2) is only used for traffic originating inside the network. The other (eth1, 192.168.1.2) is only used for a VPN, where all (udp) traffic originates from outside our network. I have created a second

ok i will do it in text: 66.92.114.46 eth0 209.141.2.194 eth1 192.168.119.101 eth2 192.168.120.101 eth3 What i have is a linux box RH7.3 which will eventually run Shorewall Firewall. On this box there is eth0 66.92.114.46 conneted to isp1 and eth1 209.141.2.194 connected to isp2 It also has eth2 192.168.119.101 and eth3 192.168.120.101 which will connect to a failover appliance which has 2 wan