similar to: email address

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 '

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.

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

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

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

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

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

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

No, the Battery Temp does not change. It is always 25C. I don't know why the ups.delay.start is that high. Is that user configurable? Yes, I have tested the automatic shutdown. Works well. 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 -----

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

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

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

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]:

My personal experience with a number of UPSes that are monitored via USB cable is that communications errors such as the ones referenced in the issue you linked to below are a result of USB hardware incompatibilities between the USB chipset and the USB port on the motherboard.*? This is NOT specific to the NUT project as it affects both apcupsd and in fact, has been reported as an issue with

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

>I'm afraid I am just the messenger - @bigon (Laurent Bigonville, on GitHub) is a Debian maintainer of NUT, and he was pointing out the >bug report filed with Debian: >https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738122 >With other drivers, we sometimes see the "did not claim interface 0 before use" error if a driver gets out of sync with its PID file, >and

1 - its on load blinking battery LEDs and not giving proper back up time . APC sua1000i nut-upsdev-request@lists.alioth.debian.org wrote: Send Nut-upsdev mailing list submissions to nut-upsdev@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev or, via email, send a message with subject or body

Hi all, we should have been found the problem. Attach the patch inclusive of this problem and the previous (Riello IDG400 wrong values & not powering off). Best regards, -----Messaggio originale----- Da: Nut-upsdev [mailto:nut-upsdev-bounces+e.parisi=riello-ups.com at lists.alioth.debian.org] Per conto di nut-upsdev-request at lists.alioth.debian.org Inviato: mercoled? 7 marzo 2018 13:03 A:

Hello, thank you for the idea. I'm already behind the permission problem, which originally apeared, but I did overcome it by rules settings. this is the result for 'ls -l /dev/bus/usb/004/007': ---- crw-rw-rw- 1 root nut 189, 390 pro 23 13:23 /dev/bus/usb/004/007 ---- Os is Debian 6.0.5 Squeeze Regards Dee Dne 22.12.2014 v 13:01 nut-upsdev-request at lists.alioth.debian.org