similar to: Step by step help for Windows Vista User?

I had upssched call the looping script, and background the process (via '&'). This seems to have resolved the problem, and eliminate the delay I was experiencing -Rob ________________________________ From: nut-upsuser-bounces@lists.alioth.debian.org [mailto:nut-upsuser-bounces@lists.alioth.debian.org] On Behalf Of Dege, Robert C. Sent: Thursday, July 21, 2005 11:04 AM To:

When the UPS starts to run on Battery, upsmon notifies upssched, and upssched runs an "onbatt script", which sends out an alert every 15 seconds via wall. When the UPS is put back on line, upsmon acknowledges this change (via WALL). However, upssched does not get notified properly, so the onbatt script continues to send alerts. About 45 seconds later, upssched acknowledges the UPS

The following scriptlet, containing a wrong password among the mount options, #!/bin/bash /bin/mount -t smbfs -o \ "netbiosname=mymachine,workgroup=group,username=user, \ password=wrongpasswd,ro,debug=4" //machine/c /mnt/dir /bin/echo "Exit $?" returns invariably mount.smbfs started (version 2.2.7a-security-rollup-fix) added interface ip=192.168.0.53

On 12/17/2013 10:43 AM, David C. Rankin wrote: > Huh? Why the : in Servname? So I just hardwired it passing the port "Servname" > as "3493" (could have just used "nut" from /etc/services): Sheepishly looking for a place to hide.... Yes there was a ':' there all right. Seems I was hit by a vi error: [12:04 phoinix:/etc/ups] # grep 3493 *.conf

O.S. Ubuntu 10.10, Maverick Meerkat 32 bit. NUT 2.4.3-1ubuntu5, package installed Belkin F6C1500-TW-RK I am having trouble starting uspd whenever I add a client from my lan to uspd.conf: LISTEN 127.0.0.1 3493 LISTEN 192.168.36.106 3493 naknight at nak-server:~$ sudo upsd -DDDD Network UPS Tools upsd 2.4.3 0.000000 listen_add: added 127.0.0.1:3493 0.000093 listen_add:

NUT recently stopped working on my debian. I'm not sure which upgrade broke it. ups.conf: [mustek] driver = megatec port = /dev/ttyS0 desc = "mustek ups" # upsd -DDDD Network UPS Tools upsd 2.4.1 listen_add: added ::1:3493 listen_add: added 127.0.0.1:3493 setuptcp: try to bind to 127.0.0.1 port 3493 listening on 127.0.0.1 port 3493 setuptcp: try to bind

$ sudo /usr/sbin/upsd -DDDD Network UPS Tools upsd 2.4.3 0.000000 listen_add: added ::1:3493 0.000084 listen_add: added 127.0.0.1:3493 0.000102 setuptcp: try to bind to 127.0.0.1 port 3493 0.000185 listening on 127.0.0.1 port 3493 0.000204 setuptcp: try to bind to ::1 port 3493 0.001328 setuptcp: socket: Address family not supported by protocol 0.001381

Hello all, I have been having a problem with upsmon on Fedora 24 on boot. NUT is configured as a netclient to a Raspbian NUT server. After boot up upsmon repeatedly says "connect failed: No such host". It is not able to connect at all until the service is bounced. This seems to indicate a name resolution problem but shouldn't this auto correct once name resolution is working properly

Bonjour ? tous, Je n'arrive pas a faire marcher NUT avec HomeAssistant. Cela fait des mois que je suis la-dessus, mais sans succ?s ! Je ne vois plus quoi faire ! Help ! * Ubuntu 23.10 * NUT version = 2.7.4-14ubuntu2 * NUT installation method: Package * exact device name and related information : Riello IDG800 Voici les commandes que je tape sur le PC connect?

First, my installation is samba 2.2.8 running as a daemon (not inetd) on Solaris 8 configured to use a WINS server and provide authentication via a PDC (same host as WINS server). I do have an lmhosts file in the samba /lib directory with the PDC/WINS server address in it. My globals section; [global] workgroup = WORKGROUP netbios name = SAMBASERVER security =

I am not sure if your problem is similar to what we have just experienced. we are using samba 2.2.3a-12.3 on debian with winxp sp1 clients we are using roaming profiles first logon after reboot fails sortof Windows cannot find a server copy of roaming profile will logon with local profile funny thing we never saw any activity in hostname.log (seperate smb.log for each machine) smbstatus showed

On 12/03/2016 10:08 AM, Charles Lepple wrote: >> On Dec 3, 2016, at 11:01 AM, Jack McGee <jack at greendesk.net> wrote: >> >> I did restart those services, no change. >> > $ ps auxww|grep [/]nut > root 13074 0.0 0.0 37844 2628 ? Ss 08:42 0:00 /lib/nut/upsmon > nut 13076 0.0 0.0 45632 5148 ? S 08:42 0:00 /lib/nut/upsmon

Talking to myself again ;-) Samba-tool is working a little bit different then the silo/policy management on a Windows-DC. On a Windows-DC after assigning the user and host to the silo you have to assign the silo to the user and the host. When assigning the user and host to the silo with samba-tool, the assignment to the user and the host will be done at the same time. So now my policy looks

Hi Stefan, We had a long weekend in New Zealand, I'm catching up now to your emails. Some of the slight differences between Windows tools I've already picked up on and are in my PR Andrew Bartlett mentioned on Friday, but I'm always open to learning what things are missing or different etc. On 23/10/23 02:58, Stefan Kania via samba wrote: > Talking to myself again ;-) > >

I have a Dell 500w UPS and it works great with Ubuntu 12.04 LTS and Network UPS tools 2.6.3 via usb. This powers a standalone server for the purposes of clean shutdowns. This was installed using "sudo apt-get install nut" and there are no issues with the Server > nut > ups chain. I am using the usbhid-ups driver and haven't had any issues. I am trying to also add an NAS to the

Thanks Rob for chiming in. Stefan, I do want to be very clear, one of the big challanges that we as developers face building these kind of tools is that we don't run AD domains day-to-day. So we really value good feedback on the ergonomics. If you can test with our work in progress, we are keen to adapt the tooling where possible to be more in line with what is 'naturally expected, so

On 12/16/2013 09:23 PM, Charles Lepple wrote: > Not sure - I didn't write the getaddrinfo() code in upsd, but it seemed to > follow all of the recommendations on how to use that function. So if there is > a way to fix it in the NUT code, I am not aware of it (and would appreciate > any updates if that turns out to be the case). > > The odd part is that it looks like you went

Device web page http://www.samurai-power.com/samurai-smart-1000-lcd UPS is marked as Micropower LCD 1000, but in Slovenia is remarked as Samurai LCD 1000 [ups] driver = blazer_usb port = auto vendorid = 0001 productid = 0000 upsc ups Init SSL without certificate database battery.charge: 100 battery.voltage: 27.40 battery.voltage.high: 26.00 battery.voltage.low: 20.80 battery.voltage.nominal:

Hello, I am trying to get nut running on a Windows 2012 R2 server (x64). I am using the MSI release of 2.6.5-3. The attached UPS is an APC xs1500 (model bx1500g). The connection is an RJ45 to USB cable. Here is my ups.conf: [xs1500] driver = usbhid-ups port = auto desc = "APC Back-UPS xs1500" The problem I am encountering is upsd crashing with an 'Out of memory' error. I can

hi, I recently upgraded my Debian Lenny system to Squeeze, and have been happily running nut as a MODE=standalone system talking to my Cyberpower 1500 avr lcd via the usbhid-ups driver for a couple of weeks or so. No problems. Now I'm trying to hang another machine off the same ups as a slave, and it isn't working. The problem I'm getting is best illustrated by what