similar to: Looking for help assigning right to AD Machine accounts..

On Thu, Aug 13, 2020 at 7:46 PM Todd Benivegna <todd at benivegna.com> wrote: > So I finally got a test in after I changed my RPi to the master and > everything else (including my Synology) to slaves. Before I did that > though, I timed the shutdown of my Synology since it is the slowest slave > to shutdown. It took 40 seconds to shutdown, so I changed HOSTSYNC in >

Larry, I have not edited a single file, including anything to do with NUT, on the Synology via ssh.... ever. How is yours configured in the UI? Do you have it set to go into safe mode after a certain number minutes? Earlier, I was just copying and pasting the contents of some files to Roger but did not change anything. -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 8:16 AM -0400,

On 20/06/2023 14:11, Ingo Asche via samba wrote: > Hi All, > > the Synology support is claiming this bug is the reason for the access > problems via hostname (Kerberos): > https://bugzilla.samba.org/show_bug.cgi?id=14213 > > These log entries in log.wb-ADNAME are given as evidence: > > ../../source3/winbindd/winbindd_msrpc.c:307: [2023/06/14 > 22:13:42.913399,

Synology ( https://www.synology.com/en-global ) is one of best selling brands of consumer/prosumer/SMB NASes, with revenue estimated to be in the $100M+ range. Several of their NAS backup options use rsync either explicitly or under the hood (NAS-to-Remote-NAS backup, Shared-Folder-Sync), and they run the rsync daemon (under File Services). rsync is an integral part of their solution. They use a

I found something interesting that I think may apply here. Check this out... https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave *I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a very old APC BK650M which is controlled and sends its status via a special serial cable to the

Hi Rowland, to be clear, I'm completely your opinion. They had a running 4.15.9(-0619, their own build number), which was a Beta, and the released version (-0632) didn't worked. So for me it's obvious, too. I can bring the released version to run with a library from their beta version: libidmap-samba4.so. The reason for this as they wrote: "A key difference between SMB

On 20/06/2023 18:30, Ingo Asche via samba wrote: > Hi Rowland, > > to be clear, I'm completely your opinion. > > They had a running 4.15.9(-0619, their own build number), which was a > Beta, and the released version (-0632) didn't worked. So for me it's > obvious, too. > > I can bring the released version to run with a library from their beta >

Sorry, I guess it is */usr/syno/bin/synoups* On Fri, Aug 14, 2020 at 2:27 PM Todd Benivegna <todd at benivegna.com> wrote: > I found something interesting that I think may apply here. Check this > out... > > > > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave > > *I have the latest version of the Windows port of NUT (A UPS

There was a Travis Wenks here, who has/had the same problems. I'm still hoping, he's reading the Samba mail list and tell me if he has still the same problems and we maybe can ally for this. Maybe the maintainers who has answered to the bug report can give some advice, too. The problem for me is that the developers from Synology think it can't be their fault. It's a little

On Fri, 14 Aug 2020, Todd Benivegna wrote: > https://forum.synology.com/enu/viewtopic.php?f=19&t=73960&hilit=ups+slave  > > I have the latest version of the Windows port of NUT (A UPS management package) installed on my Windows 7 machine. The UPS I am using is a > very old APC BK650M which is controlled and sends its status via a special serial cable to the Windows

On Thu, 13 Aug 2020, Todd Benivegna wrote: > So I finally got a test in after I changed my RPi to the master and everything > else (including my Synology) to slaves.  Before I did that though, I timed the > shutdown of my Synology since it is the slowest slave to shutdown.  It took 40 > seconds to shutdown, so I changed HOSTSYNC in upsmon.conf on the master > (“Proton”) to

Hi, Context of my question: * OS name and version, Synology's distributed Linux: Linux DS 3.10.102 #15152 SMP Fri Sep 1 11:15:03 CST 2017 x86_64 GNU/Linux * exact NUT version, Tricky... the installed tools display: $ /usr/sbin/upsd -V Network UPS Tools upsd DSM6-1-15114-170518 while the one I've compiled, and its not running, displays: $ /opt/sbin/upsd -V Network UPS Tools upsd

On Thu, Jul 13, 2023 at 11:47?AM Bo Kersey <bo at vircio.com> wrote: > The patch on Windows Server 2012 R2 that does the same thing as kb5028166 > is KB5028228 > > > ------------------------------ > > *From: *"Philippe LeCavalier" <support at plecavalier.com> > *To: *"Bo Kersey" <bo at vircio.com> > *Cc: *"samba" <samba

So I finally got a test in after I changed my RPi to the master and everything else (including my Synology) to slaves.  Before I did that though, I timed the shutdown of my Synology since it is the slowest slave to shutdown.  It took 40 seconds to shutdown, so I changed HOSTSYNC in upsmon.conf on the master (“Proton”) to 60.  I then did a test ("sudo upsmon -c fsd”). The slaves shutdown, then

Hi All, the Synology support is claiming this bug is the reason for the access problems via hostname (Kerberos): https://bugzilla.samba.org/show_bug.cgi?id=14213 These log entries in log.wb-ADNAME are given as evidence: ../../source3/winbindd/winbindd_msrpc.c:307: [2023/06/14 22:13:42.913399, winbind 3, pid=10150] msrpc_sid_to_name msrpc_sid_to_name: S-1-18-1 f?r Dom?ne ADNAME

I have the latest version of the Windows port of NUT installed on my Windows?7?machine. The UPS is connected via serial cable to the Windows machine. I also have my Synology NAS (which uses NUT) connected over the local network as a slave to the Windows NUT master. The Synology slave is configured to immediately go into "safe mode" whenever an FSD or OB+LB indication is received from the

On Mon, 10 Aug 2020, Todd Benivegna wrote: > synoups: https://hastebin.com/xexafofiha.bash Wow! What a mess. It looks as if Synology wanted to write their own "NUT", but decided it would be easier to put their ideas in a script when they saw they could use upssched.conf to call it. NUT intends such a script for timer management. Synology use it for general system management.

Thanks Larry, no problem. I appreciate the input. Whenever you get a chance I’d really like to compare notes with someone who has NUT and a Synology to see why the heck mine doesn’t work! ;). I’m also using my Pi as the master like you. Thanks. Todd -- Todd Benivegna // todd at benivegna.com On Aug 14, 2020, 11:55 AM -0400, Larry Fahnoe <fahnoe at fahnoetech.com>, wrote: > On Fri, Aug

I run a Samba4 AD and joined a Synology NAS running Samba 3.6.9. I can access the shares using smbclient or mount -t cifs from all Linux machines (usually running Samba 3.6.6 clients). I can mount the shares from WinXP home and Win7 home. However, with a Win7 Ultimate machine joined to the AD most of the time it doesn't work. I can logon to the machine with my AD credentials, but I am

Hello, I am trying to get my synology DS 418play to connect to my new INTERNET600U UPS, but it appears not to work. I contacted TrippLite and they said the unit is using a new comm protocol 3024. Is there a way to make this work with usbhid-ups? More details of my story here: https://community.synology.com/enu/forum/1/post/132984 Thanks for your help! -Troy