similar to: nut on armhf, r-pi4b IOW

On my raspbian buster RPi3's that run nut, no problems with the stock nut packages provided so I wouldn't expect problems with your RPi4 once you get the cable and configs sorted out. I use the RPi3's as nut-servers to monitor and manage my Tripp-Lite UPS systems, the other local systems run nut-client and communicate with the RPi. --Larry On Tue, Jan 7, 2020 at 6:28 AM Gene Heskett

On Wednesday 08 January 2020 09:37:10 Roger Price wrote: > On Tue, 7 Jan 2020, Gene Heskett wrote: > > ● nut-monitor.service - Network UPS Tools - power device monitor and > > shutdown controller > > Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; > > vendor preset: enabled) > > Active: failed (Result: protocol) since Tue 2020-01-07 07:19:19

Came across this in the process of troubleshooting: https://alioth-lists.debian.net/pipermail/nut-upsuser/2011-November/007249.html My whole reason for compiling from source is to add SSL support (as it doesn't seem available through the package manager). Apt list shows these installed: libusb-1.0-0-dev/stable,now 2:1.0.22-2 armhf [installed] libusb-1.0-0/stable,now 2:1.0.22-2 armhf

I got it. Thanks. The share is working. Only problem, I need some files to be only readable for the end user (templates) the problem is windows doesn't for some reason allow me to change the rights. I am using dutch windows so the error is dutch but translated it say. Can't connect/find active directory to verify or open claimtypes. Philip "Rowland penny via samba" <samba at

The output is: getent group 'domain admins? Copying without understanding what it does is not smart I know. But sometimes you will understand it later. And atm I am using a test setup. Here are is all the info you need: Main AD: Collected config --- 2020-09-05-18:16 ----------- Hostname: gaia DNS Domain: rompen.local FQDN: gaia.rompen.local ipaddress: 192.168.88.2 -----------

What I am aware of I didn?t mess with the bidmap config. But I don?t really understand what it is, and where I use it for. I am really new to samba. All I know is that I have something regarding this in my config. And that it has something to do with users and groups. Thanks a lot btw for all the help. Without it I would be stuck on things like this for weeks Philip > On 4 Sep 2020, at 18:57,

Roy, Im still wondering what your problem might be/where its coming from. But we know it's interface/network related, only thing is Samba should not coredump. So i had a good look below to see where im missing what. And i dont see much to work with. I have 2 possible options where, where a problem might be. 1) samba start before network is online. A possible workaround is add in all

On 05/02/2020 10:33, L.P.H. van Belle via samba wrote: > >> I didn't bother checking, I can cause the panic just by editing >> smb.conf, adding the two lines in question and then >> restarting Samba. I >> do this over SSH, so presumably the network is up on eth0 ;-) > Ah, ok, so we clearly have bug in samba??? > But i dont see this one on Debian Buster

On Wednesday 08 January 2020 12:01:08 Gene Heskett wrote: > On Wednesday 08 January 2020 09:37:10 Roger Price wrote: > > On Tue, 7 Jan 2020, Gene Heskett wrote: > > > ● nut-monitor.service - Network UPS Tools - power device monitor > > > and shutdown controller > > > Loaded: loaded (/lib/systemd/system/nut-monitor.service; > > > enabled; vendor

On Tue, 7 Jan 2020, Gene Heskett wrote: > ● nut-monitor.service - Network UPS Tools - power device monitor and > shutdown controller > Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; > vendor preset: enabled) > Active: failed (Result: protocol) since Tue 2020-01-07 07:19:19 EST; > 116ms ago > Process: 32343 ExecStart=/sbin/upsmon (code=exited,

Hi, I'm not sure if it is a bug or a feature. I'm running Ubuntu 20.04 on my RPi4 which connects to the UPS over USB. I have noticed whenever I reboot my RPi4. It resets the UPS ( I can hear the relay) -- Powerloss. Any pointers to disable this annoying bug / feature. ups.conf: --8<---- [tripp] driver = usbhid-ups port = auto vendorid = 09ae productid = 2009 bus

On Sunday 12 January 2020 12:09:04 Gene Heskett wrote: > On Sunday 12 January 2020 11:14:13 Charles Lepple wrote: > > On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote: > > >> Instant return, logging this: > > > > > > in /tmp/info > > > > > >> 0.000000 Error: too many non-option arguments. Try -h for > > >> help. Network

Nope, but that was not the problem... root at samba01:~# dpkg -l | grep python-dns root at samba01:~# apt-get install python-dns Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: python-dns 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 28.7 kB of archives. After this operation, 135

Is there a version of Samba that will run on a Raspberry Pi 2? If so, can somebody point me to it? If not can, Samba be compiled on a Raspberry Pi 2? Thanks for your help. -- Paul (ganci at nurdog.com) Cell: (303)257-5208

On 04/05/2020 12:59, Jelle de Jong via samba wrote: > > root at samba01:~# cat /etc/nsswitch.conf? | grep winbind > passwd:???????? files systemd winbind > group:????????? files systemd winbind OK, the only computer I have that runs systemd, is my Rpi4 running Raspbian, which is basically Buster compiled for ARM. I have in /etc/nsswitch.conf: passwd:???????? files winbind

On 5/22/23 03:10, gene heskett wrote: > Which file in the nut I pulled a month ago, should I start with to get > the new version actually running? I still get - -V=2.7.4 The UPGRADING file tsalks about a 2.8.1, but I have started with the autogen 3 times in the usual sequence, winding up with 2.7.4 twice, and while the third time is supposed yo be a charm, now it won't run at all.

But runs normally if started. On a rpi4 running an uptodate raspbian buster, how do I set it to auto start at boot time? Thanks. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) If we desire respect for the law, we must first make the law respectable. - Louis D.

I think you have just the libraries - also you'd need a *-dev package for headers. The docs/config-prereqs.txt has the dependencies in more detail. In quick practice, --with-all=auto can help better if you don't monitor a netxml device ;) HTH Jim On Mon, May 22, 2023, 15:24 gene heskett <gheskett at shentel.net> wrote: > On 5/22/23 03:10, gene heskett wrote: > > Which

On Friday 10 January 2020 07:52:47 Gene Heskett wrote: > > Not sure where that message is coming from, but glad it worked with > > the newer aclocal. (Did you use the release tarball, or a Git > > checkout?) > > Release 2.7.4 tarball. Docs are years out of date, man pages claim > 2.7.3 dated in 2015... But it works, and thats what counts. :) Got it wired up and

On Sunday 12 January 2020 11:14:13 Charles Lepple wrote: > On Jan 12, 2020, at 9:56 AM, Gene Heskett wrote: > >> Instant return, logging this: > > > > in /tmp/info > > > >> 0.000000 Error: too many non-option arguments. Try -h for > >> help. Network UPS Tools - Generic HID driver 0.41 (2.7.4) > >> USB communication driver 0.33 >