This fixed everything! Everything appears to be working ok now and all clients
are connected. Thank you!
Going to test everything out now.
--
Todd Benivegna // t...@benivegna.com
On Aug 12, 2020, 6:16 PM -0400, Charles Lepple , wrote:
> On Aug 12, 2020, at 5:32 PM, Todd Benivegna wrote:
> >
>
On Aug 12, 2020, at 5:32 PM, Todd Benivegna wrote:
>
>> Those LISTEN lines were appropriate pre-systemd when NUT's startup script
>> was launched after networking was fully enabled. I would recommend "LISTEN
>> 0.0.0.0 3493" instead, and use firewall rules if you are trying to exclude
>> an
> If you have problems with having the NAS as master, make it a slave, and run
> the
> NUT configuration of your choice in your PC/workstation.
I have done just this. I changed the Synology to a slave and made my Raspberry
Pi master and the rest of my servers are slaves as well. Manuel
555 gives no write access to the dir, and the files are covered by their
own perms, so I fail to see any relevance to your comment - sorry . . .
640 is decent for files, not so much for directories - as noted, the
fields mean different things on dirs . . .
From the man pages:
The
On Aug 12, 2020, at 12:11 AM, Todd Benivegna wrote:
>
> Here is my upsd.conf:
>
> LISTEN 127.0.0.1 3493
> LISTEN 192.168.1.31 3493
>
Those LISTEN lines were appropriate pre-systemd when NUT's startup script was
launched after networking was fully enabled. I would recommend "LISTEN 0.0.0.0
Synology, in their NAS products, include NUT for UPS based power management. But
although Synology use upsd to talk to the UPS unit, they have their own power
management software called "Safe Mode". This reduces upsmon and upssched to
pure passthrough with the status changes handled by
The only reason NUT may whant to modify it's config is NUT-CGI and may be
Synology GUI.
Even then default install on my Synology makes no trubble.
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
On 8/12/20 8:10 AM, Tim Dawson wrote:
For directory permissions, the "x" priv determines if you can access
the directory, so going from 555 (r-x,r-x,r-x) to 640 (rw-,r--,---)
pretty much locks out access to the dir. Myself, I'd go back to 555.
640 essentially locks the group "nut" out . . .
On 8/12/20 7:11 AM, Todd Benivegna wrote:
Ok, so just a follow-up to my last email; still following that guide,
which is great…. Just stuck on getting the nut-server service starting
automatically. Got everything else working. I’ve been able to get
the nut-client starting up automatically at
On Wed, 12 Aug 2020, Manuel Wolfshant wrote:
So nut on Synology believes that it is a good idea to trigger a FSD 30 secs
AFTER switching back to line power when in fact it should CANCEL any shutdown
in progress. Unless you have the willingness to search & fix whatever
stupidities they do in
10 matches
Mail list logo
