Sounds great Roger!
I have upgraded myself from 13.2 to 42.1.
Looking forward to hearing from you :)
---
George
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
On Wed, 2 Dec 2015, George Anchev wrote:
Did find a solution regarding the wall notifications?
Hello George, I'm still struggling to install openSUSE 42.1 with KDE.
When I have this (almost) working, I will have a look at the effect of
wall on KDE.
Roger
___
Hi Roger,
Are you getting my messages?
---
George Anchev
On Mon, Nov 9, 2015 at 5:54 PM, George Anchev wrote:
> Hi Roger,
>
> Did find a solution regarding the wall notifications?
>
> ---
> George
>
___
Nut-upsuser mailing list
Nut-upsuser@lists.alio
Hi Roger,
Did find a solution regarding the wall notifications?
---
George
___
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
>
> I'll look at this, but it will be next week at the earliest.
Great! Could you please notify when you do it?
Meantime your change to the NOTIFYFLAGs is a good fix.
Thanks.
At present I don't have an example, perhaps others could advise you.
I hope.
---
George
___
On Thu, 29 Oct 2015, George Anchev wrote:
Today I experienced something weird. As I was working, the system
started a shutdown and did shut down, then the UPS got powered off and
then back on - an expected behavior for a power fail situation. However
there was no power failure!
...
Oct 29 1
On Wed, 28 Oct 2015, George Anchev wrote:
P.S. There is a typo in your nut-delayed-ups-shutdown.service. Line:
ExecStart=/usr/bin/logger -t upsdrvctl "nut-delayed-ups-shudown.service calling
upsdrvctl to shut down UPS unit"
shudown is missing a 't'. It is in the log message but might still be
>
> I don't know if upsmon is running as root or upsd when it calls wall for a
> shutdown. If it is running as upsd then there could be a problem.
It seems running as upsd, otherwise it makes no sense not to work. However
upsd user doesn't have a shell (I see /bin/false as it's shell in YaST >
U
On Wed, 28 Oct 2015, George Anchev wrote:
${sbinPath}upsmon -c fsd
In 'upsmon --help' I read: "- fsd: shutdown all master UPSes (use with
caution)". What exactly does this line do?
My understanding is that it calls upsmon running as root to execute the
command specified by SHUTDOWNCMD in up
P.S.2
Today I experienced something weird. As I was working, the system started a
shutdown and did shut down, then the UPS got powered off and then back on -
an expected behavior for a power fail situation. However there was no power
failure!
I ran nut-journal to check what happened:
Pre
P.S. There is a typo in your nut-delayed-ups-shutdown.service. Line:
ExecStart=/usr/bin/logger -t upsdrvctl "nut-delayed-ups-shudown.service
calling upsdrvctl to shut down UPS unit"
shudown is missing a 't'. It is in the log message but might still be worth
fixing for grepping.
BTW why is that s
>
> Did you see a line in the journal similar to this ?
> Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]:
> nut-delayed-ups-shudown.service calling
> upsdrvctl to shut down UPS unit
Never after I disabled the service. I pasted the whole journal section of
On Wed, 28 Oct 2015, George Anchev wrote:
Beautiful! The shutdown succeeded.
Did you see a line in the journal similar to this ?
Oct 06 22:49:54 pinta nut-delayed-ups-shutdown[1854]:
nut-delayed-ups-shudown.service calling
upsdrvctl to shut down UPS unit
H
Beautiful! The shutdown succeeded. Thank you very much. However there was
no any notification on desktop at all. Only in journalctl. Here it is:
Oct 27 23:38:11 i7 upsmon[2224]: UPS myups@localhost on battery
Oct 27 23:38:11 i7 upssched[2244]: Timer daemon started
Oct 27 23:38:11 i7 upssched[2244]
On Tue, 27 Oct 2015, George Anchev wrote:
Yes, that was the power off test. However the upssched-cmd script gave
absolutely no signs of activity. Even it's logger lines don't show up in
journalctl. No any permission error messages - nothing. Only the 2
messages from upsmon - on battery and the
Yes, that was the power off test. However the upssched-cmd script gave
absolutely no signs of activity. Even it's logger lines don't show up in
journalctl. No any permission error messages - nothing. Only the 2 messages
from upsmon - on battery and then on line power.
Here is the nut-report:
http
On Tue, 27 Oct 2015, George Anchev wrote:
Oct 26 21:02:56 i7 upsd[2227]: Startup successful
...
Oct 26 21:02:56 i7 upsmon[2229]: Startup successful
...
Oct 26 21:04:51 i7 upsmon[2230]: UPS myups@localhost on battery
Oct 26 21:05:11 i7 upsmon[2230]: UPS myups@localhost on line power
Power w
Yes:
Previous complete boot through shutdown
Oct 26 21:02:54 i7 upsdrvctl[1955]: Using subdriver: MGE HID 1.32
Oct 26 21:02:55 i7 upsdrvctl[1955]: Network UPS Tools - Generic HID driver
0.38 (2.7.1)
Oct 26 21:02:55 i7 upsdrvctl[1955]: USB communication driver 0.32
Oct 26 21:02:56 i7 upsdrvctl[1955
On Mon, 26 Oct 2015, George Anchev wrote:
Hello,
I have been following the details in this article to configure my UPS:
http://rogerprice.org/NUT.html
However the system won't shutdown although file permissions look ok:
ls -alF /usr/sbin/ups*
-rwxr--r-- 1 upsd daemon 64984 Oct 15 2014 /usr/s
Hello,
I have been following the details in this article to configure my UPS:
http://rogerprice.org/NUT.html
However the system won't shutdown although file permissions look ok:
ls -alF /usr/sbin/ups*
-rwxr--r-- 1 upsd daemon 64984 Oct 15 2014 /usr/sbin/upsd*
-rwxr--r-- 1 upsd daemon 48584 Oct
20 matches
Mail list logo