search for: jsamcr

...e message from there. ?Is that peculiar? Might account for why I am notgetting anything from ' wall ' . John?"Science is organized common sense. Philosophy is organized piffle" -attributed to Bertrand Russel From: Tim Dawson <tadawson at tpcsvc.com> To: john hart <jsamcr at yahoo.com>; NUT Developers <nut-upsdev at lists.alioth.debian.org> Sent: Wednesday, July 15, 2015 8:52 PM Subject: Re: [Nut-upsdev] Good news Who is the owner and group for wall? Note that it is set group ID to allow it to write to sessions . . . thus, that owner needs to be a sy...

...e ? rwxr-sr-x ?and the filename is has a ?kind of orange highlightedbackground. Don't know what that means. John?"Science is organized common sense. Philosophy is organized piffle" -attributed to Bertrand Russel From: Tim Dawson <tadawson at tpcsvc.com> To: john hart <jsamcr at yahoo.com>; NUT Developers <nut-upsdev at lists.alioth.debian.org> Sent: Wednesday, July 15, 2015 7:43 PM Subject: Re: [Nut-upsdev] Good news Any chance someone put 'mesg n' in the system profiles? That wou;d suppress wall output. Try typing just 'mesg' and see wh...

..., as when using theNUT-Monitor program I get banners and a 'message' on the system try. ? Strange ! John ??"Science is organized common sense. Philosophy is organized piffle" -attributed to Bertrand Russel From: Charles Lepple <clepple at gmail.com> To: john hart <jsamcr at yahoo.com> Cc: NUT Developers <nut-upsdev at lists.alioth.debian.org> Sent: Wednesday, July 15, 2015 6:12 PM Subject: Re: Good news On Jul 15, 2015, at 12:38 PM, john hart <jsamcr at yahoo.com> wrote: > So, the system shut down and turned off the UPS, which is exactly...

ls -lia /<path>/wall will give you the owner and group . . . . Messages off . . . I think you are on the path . . . . -Tim On July 15, 2015 10:00:51 PM CDT, john hart <jsamcr at yahoo.com> wrote: >Time, not sure who owner is, but I've tried as both admin and myself, >to no avail. ?However, I told you that mesg is y, buti tried to send a >mesg using ?' write ' ?and it says I have messages disabled. ????? ? I >did that by opening two?terminals,...

...wall? Note that it is set group ID to allow it to write to sessions . . . thus, that owner needs to be a system account that can write to devices, not just Joe-Bob . . . You might also try 'strace wall' to see what it is trying to do. - Tim On July 15, 2015 9:48:32 PM CDT, john hart <jsamcr at yahoo.com> wrote: >Tim, >Thanks for the feedback. ?I am the only user (standalone system), but I >checked 'mesg' and made sure it was set?to 'mesg y' . ? And the execute >permissions for wall are ? rwxr-sr-x ?and the filename is has a ?kind >of orange highlighte...

Charles, This is how I have the upsmon.conf set up. ?The only time I get a message is if the?NUT Monitor gui is running. ?I open LXterminal, pull the wall plug, and I get no messagesin the terminal. ?MONITOR Asium_p700 at localhost 1 upsmon jsamcr master?MINSUPPLIES 1?SHUTDOWNCMD "/sbin/shutdown -h +0"?NOTIFYCMD /sbin/upssched?POLLFREQ 5?POLLFREQALERT 5?HOSTSYNC 15?DEADTIME 15?POWERDOWNFLAG /etc/killpower # NOTIFYMSG - change messages sent by upsmon when certain events occur# You can change the default messages to something else if...

I tested shutdown by pulling the plug from the wall socket and observed that I was notgetting any notifications. ?Then I opened the NUT Monitor GUI and immediately got notified. What did I do wrong? ?I think that upsmon runs at startup so why do I have to open the GUI?in order to get messages? ? John?"Science is organized common sense. Philosophy is organized piffle" -attributed to

Any chance someone put 'mesg n' in the system profiles? That wou;d suppress wall output. Try typing just 'mesg' and see what it says . . . otherwise, check permissions on wall perhaps . . . - Tim On July 15, 2015 7:43:38 PM CDT, john hart <jsamcr at yahoo.com> wrote: >Tried 'echo hi | wall' and no message. ?I looked at 'wall -h' and it >would seem that it is supposed to. ?I eventried ?' wall ?[<filename> | ><message>] ' ?and got nothing. ? Not sure what that means, as when >using theNUT-Mon...

Please use Reply-All. On Jul 13, 2015, at 11:00 PM, john hart <jsamcr at yahoo.com> wrote: > Okay. I went through the pages from Roger Price and have set up enough, I think that I > should at least get an 'OL' response when I run 'upsdrvctl start' . Instead I get this: > [CODE] > root at debian:/home/john# upsdrvctl start > Netw...

As an update to my first message, sent July 13, I am totally out of my league.I installed nut (apt-get install nut) on Debian Jessie. ?Went through the process of modifying?ups.conf and copied the udev ( cp /lib/udev/rules.d/52-nut-usbups.rules /etc/udev/rules.d/ ) When I ran ?upsdrvctl start ?I got a message about the usbhid-ups driver. ?It appears that NUTis not configured with the driver. ?The

I pulled the AC power and let the system shutdown. ?Everything appears to have gone well. ?Checked thesystem log and found the following sequence of events: [CODE] Jul 15 10:20:50 debian upsmon[678]: UPS 1 on batteryJul 15 10:26:05 debian upsmon[678]: UPS 1 battery is lowJul 15 10:26:05 debian upsd[675]: Client upsmon at 127.0.0.1 set FSD on UPS [Asium_p700]Jul 15 10:26:05 debian upsmon[678]:

On Sep 22, 2015, at 11:27 AM, Thomas Charron <twaffle at gmail.com> wrote: > > On Tue, Sep 22, 2015 at 9:56 AM, John Hart <jsamcr at gmail.com> wrote: >> notify-send > > notify-send needs a DBUS_SESSION_BUS_ADRESS to work right. Look around for code snippets to get this. Ah, that notify-send. Another option is to launch the PyNUT app in your xsession (or equivalent) - it will also display GUI notifications....

Either I am missing something or I am really STUPID. 1. I have added a user, named nutmon, to the nut group. 2. In upsmon.conf I have set RUN_AS_USER nutmon . 3. I have NOTIFYCMD /etc/nut/notifyme.sh and it is set as 755, so should be executable by everyone. 4. I have the NOTIFYFLAG set as SYSLOG+WALL+EXEC, so the shell should execute. This is the shell script : #!/bin/bash # # NUT NOTIFYCMD

Greetings.? I have been using NUT for some time now and have not had any issues until yesterday.? I was trying to get my NOTIFYCMD script working and was making modifications to upsmon.conf .? After making the mod to upsmon.conf I invoked upsmon -c reload and a few minutes later the system shut down.? There was a loss of communications with the UPS.? I have an Asium P700 UPS and use the blazer_usb

.... Yes, the instant commands work, at least those I feel comfortable testing. Battery test work fine. I have not enable the write to variables. Did not know that it might be necessary. John Hart ----- Forwarded Message ----- *From:* Charles Lepple <clepple at gmail.com> *To:* john hart <jsamcr at yahoo.com> *Cc:* "nut-upsdev at lists.alioth.debian.org" < nut-upsdev at lists.alioth.debian.org> *Sent:* Sunday, September 20, 2015 2:52 PM *Subject:* Re: [Nut-upsdev] [HCL] Asium P700 On Sep 19, 2015, at 10:08 AM, john hart <jsamcr at yahoo.com> wrote: > > I hav...

Looking in to my previous question about no messages until clicking NUT Monitor GUI,I found that it was recommend to make sure that /etc/default/nut ?should be as follows: # /etc/default/nut START_UPSD=yes START_UPSMON=yesHowever, there is no '/etc/default/nut' . ? Do I need to create it ? John? "Science is organized common sense. Philosophy is organized piffle" -attributed to

On Jul 14, 2015, at 3:48 PM, john hart <jsamcr at yahoo.com> wrote: > I tested shutdown by pulling the plug from the wall socket and observed that I was not > getting any notifications. Then I opened the NUT Monitor GUI and immediately got notified. > > What did I do wrong? I think that upsmon runs at startup so why do I have...

On Jul 14, 2015, at 8:10 PM, john hart <jsamcr at yahoo.com> wrote: > This is how I have the upsmon.conf set up. The only time I get a message is if the > NUT Monitor gui is running. I open LXterminal, pull the wall plug, and I get no messages > in the terminal. Hopefully someone else on the list can help with the NUT Monitor G...

On Jul 15, 2015, at 12:38 PM, john hart <jsamcr at yahoo.com> wrote: > So, the system shut down and turned off the UPS, which is exactly what I would have expected. Also, when I > reconnected the AC power the system did NOT automatically start up, which again is what I would have wanted, > and hoped for. Good to hear! > So,...

I just looked at the ups.conf file and noticed that I have ondelay=40. Should that not have overwritten the value shown for ups.delay.start? Perhaps this UPS is not ready for prime time ! However it works okay for me. John Hart -------------- next part -------------- An HTML attachment was scrubbed... URL: