search for: logread

Thanks for your support, Jim. I found a workaround: logread showed some access-denied errors, and because I don't know exactly what it may be (except the lack of udev rules perhaps), I ran upsd as root and it connected with the UPS. Therefore I wonder whether a more elegant solution could be used for this part? But there are several things about the re...

....255.0 # cat /etc/tinc/ffnw/tinc.conf Name = tinc_FF_OS_Lagerhalle_Offloader Devive = /dev/net/tun ConnectTo = master # cat /etc/tinc/ffnw/hosts/tinc_FF_OS_Lagerhalle_Offloader Subnet = 10.0.1.10 -----BEGIN RSA PUBLIC KEY----- <...> -----END RSA PUBLIC KEY----- # tincd -n ffnw -d5; logread | grep tinc Tue Aug 1 11:06:34 2017 daemon.notice tinc.ffnw[13461]: tincd 1.0.26 (Jan 31 2016 22:35:28) starting, debug level 5 Tue Aug 1 11:06:34 2017 daemon.err tinc.ffnw[13461]: Name for tinc daemon required! Tue Aug 1 11:06:34 2017 daemon.notice tinc.ffnw[13461]: Terminating any ideas? if y...

...m github master on any other system with `make dist`. I suppose you cross-build the OpenWRT images on a capable system already?.. Jim On Mon, May 8, 2023, 17:08 Feliciano Chavez <chavezfeliciano at hotmail.com> wrote: > Thanks for your support, Jim. > > I found a workaround: > logread showed some access-denied errors, and because I don't know exactly > what it may be (except the lack of udev rules perhaps), I ran upsd as root > and it connected with the UPS. Therefore I wonder whether a more elegant > solution could be used for this part? > > But there are sev...

I'm mostly not online for a few more days, so can't check directly. The general answers to the two questions would be: 1) checking if it is there: * revise if it is mentioned in the NEWS file (in sources - release tarball or on github); * check issues on github; * search/grep for 3024 in current/release-tagged codebase... 2) getting it to your system: versioning looks debianish, some