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'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
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
>
> 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 >
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:
6 matches
Mail list logo
