similar to: Good news

Displaying 20 results from an estimated 100 matches similar to: "Good news"

2015 Jul 15
3
No messages
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
2015 Jul 16
2
Good news
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-Monitor program I get banners and a 'message' on the system try. ? Strange ! John ??"Science is organized common sense. Philosophy
2015 Jul 16
2
Good news
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, on I logged in as ' su ', and sent the message from there. ?Is that peculiar? Might account for why I am notgetting anything from
2015 Jul 16
2
Good news
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 highlightedbackground. Don't know what that means. John?"Science is organized common sense. Philosophy is organized piffle" -attributed to
2015 Jul 14
2
Strange
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
2015 Jul 13
2
Totally beyond me
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
2015 Jul 14
1
no /etc/default/nut
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
2015 Jul 16
0
Good news
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 '
2015 Jul 16
0
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 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.
2016 May 25
0
Tripplite SMART2200VS with tripplite_usb: UPS doesn't shut down
Hello, I have a Tripplite SMART2200VS that isn't being shut down when the nut master asks it to. My initial test was simply upsmon -c fsd which caused the system to shut down, but the UPS remained on and providing power to its loads. Looking in the logs (daemon and syslog) it was not clear to me that NUT was telling the UPS to shut down (I was expecting to see "Shutting down the UPS
2015 Sep 22
2
NOTIFYCMD shell script problem driving me NUTS
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
2015 Sep 23
4
NOTIFYCMD shell script problem driving me NUTS
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
2015 Nov 21
2
lost communication with UPS
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
2015 Jul 14
1
New questions
Here is the previous email that I sent directly to Charles Lepple. ?I am now sending to the correct email with cc to Charles. ---------------- I am looking at, and trying to understand the rest of the conf files. ?But first want to askabout something from this message:[CODE]root at debian:/home/john# upsdrvctl startNetwork UPS Tools - UPS driver controller 2.7.2Network UPS Tools - Megatec/Q1
2016 May 25
2
Tripplite SMART2200VS with tripplite_usb: UPS doesn't shut down
Please ignore the previous message as I sent it before it was complete. Hello, I have a Tripplite SMART2200VS that isn't being shut down when the nut master asks it to. My initial test was simply upsmon -c fsd which did cause the system to shut down, however the UPS remained on and providing power to its loads. Looking in the logs (daemon and syslog) it was not clear to me that NUT was
2015 Jul 16
0
Good news
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
2015 Jul 14
0
Totally beyond me
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 > Network UPS Tools - UPS driver
2015 Sep 21
1
Regarding the Asium P700
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:
2015 Sep 21
1
problem with NOTIFYCMD
After some testing, I notice that my NOTIFYCMD script seems to work if I call it as user 'john' (that's me) but if I call it as 'root' it does not work. So is there a permissions issue ? I have permission on the file set to 755. I see there is a variable in upsmon.conf called RUN_AS_USER. I do not have this defined. Does this variable need to be defined ? I presume that if
2015 Nov 21
1
Some thoughts on loss of communication
As a follow up on my last message, where I talked about loss of USB communication with my Asium P700 UPS, I was thinking about some possible improvements.? 1.? When communications are lost, instead of shutting down immediately why not set a flag and then stop the driver and then restart the driver.? If communication is not re-established, and the flag was set, then shut down the system.? Perhaps