May 2023 - openSUSE Users - openSUSE Mailing Lists

Leap155 - cron issue
by Per Jessen 15 May '23

15 May '23

I'm having an issue with a new cronjob - the machine is running leap155. I have a userid "dns24" which originally had a homedir of "/srv/dns24". We decided not to use that after all, but didn't change and then noticed these in the log: 2023-05-14T18:41:01+02:00 dns24 systemd[1]: Started User Manager for UID 111. 2023-05-14T18:41:01+02:00 dns24 systemd[1]: Started Session c17 of User dns24. 2023-05-14T18:41:01+02:00 dns24 cron[26821]: pam_unix(crond:session): session opened for user dns24 by (uid=0) 2023-05-14T18:41:01+02:00 dns24 CRON[26831]: (dns24) CMD (make -r -C /srv/dns24.admin -f Makefile.database) 2023-05-14T18:41:01+02:00 dns24 CRON[26831]: (CRON) ERROR chdir failed (/srv/dns24): No such file or directory ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2023-05-14T18:41:01+02:00 dns24 CRON[26821]: (dns24) CMDEND (make -r -C /srv/dns24.admin -f Makefile.database) 2023-05-14T18:41:01+02:00 dns24 CRON[26821]: pam_unix(crond:session): session closed for user dns24 2023-05-14T18:41:01+02:00 dns24 systemd[1]: session-c17.scope: Deactivated successfully. Ah, forgot to change the homedir. Changed the homedir using yast. 2023-05-14T18:46:01+02:00 dns24 systemd[1]: Started User Manager for UID 111. 2023-05-14T18:46:01+02:00 dns24 systemd[1]: Started Session c22 of User dns24. 2023-05-14T18:46:01+02:00 dns24 cron[30866]: pam_unix(crond:session): session opened for user dns24 by (uid=0) 2023-05-14T18:46:01+02:00 dns24 CRON[30876]: (dns24) CMD (make -r -C /srv/dns24.admin -f Makefile.database) 2023-05-14T18:46:01+02:00 dns24 CRON[30876]: (CRON) ERROR chdir failed (/srv/dns24): No such file or directory 2023-05-14T18:46:01+02:00 dns24 CRON[30866]: (dns24) CMDEND (make -r -C /srv/dns24.admin -f Makefile.database) 2023-05-14T18:46:01+02:00 dns24 CRON[30866]: pam_unix(crond:session): session closed for user dns24 2023-05-14T18:46:01+02:00 dns24 systemd[1]: session-c22.scope: Deactivated successfully. 2023-05-14T18:46:12+02:00 dns24 systemd[1]: Stopping User Manager for UID 111... nscd picked up the change: 2023-05-14T18:45:17+02:00 dns24 nscd[605]: 605 monitored file `/etc/passwd` was written to 2023-05-14T18:45:17+02:00 dns24 nscd[605]: 605 monitored file `/etc/passwd` was moved into place, adding watch yes, /etc/passwd has the new homedir and the new homedir exists. I'm sure I can reboot and all will be well, but .... -- Per Jessen, Zürich (12.3°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

4 7

[oS-en] About Nokogiri in Leap 15.5
by Carlos E. R. 13 May '23

13 May '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I get this warning when starting yast over ssh: Beta:~ # yast2 sw_single & [1] 2393 Beta:~ # WARNING: Nokogiri was built against LibXML version 2.9.14, but has dynamically loaded 2.10.3 [1]+ Done yast2 sw_single Beta:~ # Id this a problem? - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZF513Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV3HkAn1sHOtLBNCuwXDCQ04sO OMxkQzXcAJ4konNv84lRPhvyUrnBY9G4kDi/wA== =NqEY -----END PGP SIGNATURE-----

6 9

logrotate preremove script not working - 2nd pair of eyes ?
by Per Jessen 10 May '23

10 May '23

I just want to check I'm not going bonkers. >From the logrotate man page: --------------- preremove script endscript The script is executed once just before removal of a log file. logrotate will pass the name of file which is soon to be removed as the first argument to the script. See also firstaction and the SCRIPTS section. -------------- So it sounds reasonable to expect "script" to be invoked with one argument, the name of the to-be-removed file. Right? the logrotate config - it is a test-setup, for rotating /var/log/testfile when it exceeds 1k, without date extension. ---------------- /var/log/testfile { compress nodateext maxage 365 rotate 5 missingok notifempty size 1k sharedscripts postrotate /usr/bin/true endscript preremove /usr/local/bin/archive_logfile.sh endscript } ------------------- My script /usr/local/bin/archive_logfile.sh contains #!/bin/sh test -n "$1" || exit 75 log="$1" plus the rest When I run a logrotate (either with systemd or manually), it does invoke the preremove script, but without the filename as argument, so my script leaves with a 75. -- Per Jessen, Zürich (12.9°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

4 11

Bonding?
by Lew Wolfgang 10 May '23

10 May '23

Hi Folks, We've been collecting data through four 1-GbE Ethernet interfaces configured as independent connections on different subnets. This has been working well enough for years. But now someone has suggested bonding those four interfaces into one virtual interface. I've never had any experience with this sort of thing, it looks like there's "bonding" and a newer thing called "teaming". We're already getting 950-Mb/channel so we'd be looking more for load-leveling and fall-over reliability. I wonder if any of you might have some suggestions or experience you might share? Regards, Lew

5 14

[oS-en] dnsmasq problem
by Carlos E. R. 10 May '23

10 May '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Out of the blue, I get this in the warning log: <3.4> 2023-05-08T04:18:44.183546+02:00 Telcontar dnsmasq 23788 - - ignoring nameserver 127.0.0.1 - local interface <3.4> 2023-05-08T04:18:49.645319+02:00 Telcontar dnsmasq 23788 - - ignoring nameserver 127.0.0.1 - local interface <3.4> 2023-05-08T04:21:01.096723+02:00 Telcontar dnsmasq 23788 - - ignoring nameserver 127.0.0.1 - local interface <3.4> 2023-05-08T04:21:09.760416+02:00 Telcontar dnsmasq 23788 - - ignoring nameserver 127.0.0.1 - local interface <3.4> 2023-05-08T04:21:21.241287+02:00 Telcontar dnsmasq 23788 - - ignoring nameserver 127.0.0.1 - local interface <3.4> 2023-05-08T04:21:29.788952+02:00 Telcontar dnsmasq 23788 - - ignoring nameserver 127.0.0.1 - local interface It repeats and repeats. In the messages log, there is more stuff: <3.6> 2023-05-08T04:21:09.760027+02:00 Telcontar avahi-daemon 1264 - - Files changed, reloading. <3.6> 2023-05-08T04:21:09.760195+02:00 Telcontar dnsmasq 23788 - - reading /etc/resolv.conf <3.6> 2023-05-08T04:21:09.760246+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 for domain zen.spamhaus.org <3.6> 2023-05-08T04:21:09.760271+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 for domain valinor <3.6> 2023-05-08T04:21:09.760296+02:00 Telcontar avahi-daemon 1264 - - No service file found in /etc/avahi/services. <3.6> 2023-05-08T04:21:09.760316+02:00 Telcontar dnsmasq 23788 - - using nameserver 80.58.61.250#53 <3.6> 2023-05-08T04:21:09.760337+02:00 Telcontar dnsmasq 23788 - - using nameserver 80.58.61.254#53 <3.6> 2023-05-08T04:21:09.760359+02:00 Telcontar dnsmasq 23788 - - using nameserver 1.1.1.1#53 <3.6> 2023-05-08T04:21:09.760377+02:00 Telcontar dnsmasq 23788 - - using nameserver 1.0.0.1#53 <3.6> 2023-05-08T04:21:09.760395+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 for domain scar.opensuse.org <3.4> 2023-05-08T04:21:09.760416+02:00 Telcontar dnsmasq 23788 - - ignoring nameserver 127.0.0.1 - local interface <3.6> 2023-05-08T04:21:09.760442+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 <3.6> 2023-05-08T04:21:09.760461+02:00 Telcontar dnsmasq 23788 - - using nameserver 2a02:9000::aaaa#53 <3.6> 2023-05-08T04:21:09.760482+02:00 Telcontar dnsmasq 23788 - - using only locally-known addresses for valinor <3.6> 2023-05-08T04:21:21.240605+02:00 Telcontar avahi-daemon 1264 - - Files changed, reloading. <3.6> 2023-05-08T04:21:21.240870+02:00 Telcontar dnsmasq 23788 - - reading /etc/resolv.conf <3.6> 2023-05-08T04:21:21.240956+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 for domain zen.spamhaus.org <3.6> 2023-05-08T04:21:21.241003+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 for domain valinor <3.6> 2023-05-08T04:21:21.241045+02:00 Telcontar dnsmasq 23788 - - using nameserver 80.58.61.250#53 <3.6> 2023-05-08T04:21:21.241086+02:00 Telcontar avahi-daemon 1264 - - No service file found in /etc/avahi/services. <3.6> 2023-05-08T04:21:21.241129+02:00 Telcontar dnsmasq 23788 - - using nameserver 80.58.61.254#53 <3.6> 2023-05-08T04:21:21.241170+02:00 Telcontar dnsmasq 23788 - - using nameserver 1.1.1.1#53 <3.6> 2023-05-08T04:21:21.241208+02:00 Telcontar dnsmasq 23788 - - using nameserver 1.0.0.1#53 <3.6> 2023-05-08T04:21:21.241246+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 for domain scar.opensuse.org <3.4> 2023-05-08T04:21:21.241287+02:00 Telcontar dnsmasq 23788 - - ignoring nameserver 127.0.0.1 - local interface <3.6> 2023-05-08T04:21:21.241333+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 <3.6> 2023-05-08T04:21:21.241369+02:00 Telcontar dnsmasq 23788 - - using only locally-known addresses for valinor <10.6> 2023-05-08T04:21:22.441402+02:00 Telcontar auth - - - gkr-pam: stashed password to try later in open session <3.6> 2023-05-08T04:21:24.021009+02:00 Telcontar dbus-daemon 6408 - - [session uid=1000 pid=6408] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.79' (uid=1000 pid=8713 comm="/usr/lib/tracker-miner-fs-3 ") <3.6> 2023-05-08T04:21:24.157150+02:00 Telcontar dbus-daemon 6408 - - [session uid=1000 pid=6408] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' <3.6> 2023-05-08T04:21:27.905271+02:00 Telcontar dbus-daemon 6408 - - [session uid=1000 pid=6408] Activating service name='org.freedesktop.thumbnails.Thumbnailer1' requested by ':1.31' (uid=1000 pid=6665 comm="Thunar --sm-client-id 295296eba-ae66-485a-b5d5-5eb") <3.6> 2023-05-08T04:21:28.023852+02:00 Telcontar dbus-daemon 6408 - - [session uid=1000 pid=6408] Successfully activated service 'org.freedesktop.thumbnails.Thumbnailer1' <3.6> 2023-05-08T04:21:29.788388+02:00 Telcontar avahi-daemon 1264 - - Files changed, reloading. <3.6> 2023-05-08T04:21:29.788690+02:00 Telcontar dnsmasq 23788 - - reading /etc/resolv.conf <3.6> 2023-05-08T04:21:29.788741+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 for domain zen.spamhaus.org <3.6> 2023-05-08T04:21:29.788769+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 for domain valinor <3.6> 2023-05-08T04:21:29.788797+02:00 Telcontar dnsmasq 23788 - - using nameserver 80.58.61.250#53 <3.6> 2023-05-08T04:21:29.788824+02:00 Telcontar avahi-daemon 1264 - - No service file found in /etc/avahi/services. <3.6> 2023-05-08T04:21:29.788847+02:00 Telcontar dnsmasq 23788 - - using nameserver 80.58.61.254#53 <3.6> 2023-05-08T04:21:29.788874+02:00 Telcontar dnsmasq 23788 - - using nameserver 1.1.1.1#53 <3.6> 2023-05-08T04:21:29.788902+02:00 Telcontar dnsmasq 23788 - - using nameserver 1.0.0.1#53 <3.6> 2023-05-08T04:21:29.788926+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 for domain scar.opensuse.org <3.4> 2023-05-08T04:21:29.788952+02:00 Telcontar dnsmasq 23788 - - ignoring nameserver 127.0.0.1 - local interface <3.6> 2023-05-08T04:21:29.788981+02:00 Telcontar dnsmasq 23788 - - using nameserver 192.168.1.16#53 <3.6> 2023-05-08T04:21:29.789006+02:00 Telcontar dnsmasq 23788 - - using nameserver 2a02:9000::aaaa#53 <3.6> 2023-05-08T04:21:29.789031+02:00 Telcontar dnsmasq 23788 - - using only locally-known addresses for valinor Why is this reloading and spamming the logs hapening, out of the blue? I'm certainly not changing /etc/resolv.conf. But something is: Telcontar:~ # l /etc/resolv.conf lrwxrwxrwx 1 root root 30 Nov 29 20:24 /etc/resolv.conf -> /var/run/netconfig/resolv.conf Telcontar:~ # l /var/run/netconfig/resolv.conf - -rw-r--r-- 1 root root 688 May 8 04:21 /var/run/netconfig/resolv.conf Telcontar:~ # date Mon May 8 04:24:55 CEST 2023 Telcontar:~ # Telcontar:~ # l /var/run/netconfig/resolv.conf - -rw-r--r-- 1 root root 661 May 8 04:26 /var/run/netconfig/resolv.conf Telcontar:~ # date Mon May 8 04:26:23 CEST 2023 Telcontar:~ # Ideas? - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZFheShwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVBQYAnAyQiQ18nCU9Hi1JPEXv wjD9V4uYAJ9Ooq69yrQkKkFwGf2AJp6JTbLGfw== =z6MC -----END PGP SIGNATURE-----

5 51

Re: mostly about dnsmasq [solved] and /run/wicked/leaseinfo.eth0.auto.ipv6 changing too fast [pending]
by Carlos E. R. 10 May '23

10 May '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 (I took me more than an hour to carefully compose this message, trying to explain everything) El 2023-05-09 a las 09:05 +0200, Per Jessen escribió: > Carlos E. R. wrote: >> On 2023-05-08 23:24, Per Jessen wrote: >>> Carlos E. R. wrote: >>> >>>> >>>> >>>> Thus, I can not use NETCONFIG_DNS_POLICY="auto". >>> >>> Thus you have concluded wrongly. Using 'auto' does what is expected, >>> it updates your /etc/resolv.conf when the information changes. >> >> But I don't want it to contain that information. > > Here the pertinent question is probably - why not? > >> I need /etc/resolv.conf to point only at my local or LAN DNS servers, >> not the remote ones. > > Why? > >> AND, I can not use a file that changes every minute, even if I wanted >> what it contains! > > Well, although it is of course too much, it would still work. (with a lot of noise in the logs. I can not stand that, it drives me nuts. I was trained to analyze logs, it was my job. That is the problem that started this thread, noise in the logs). Per, I'll try to explain again. The way dnsmasq works, it *has* to be configured this way (if using wicked): /etc/resolv.conf: 127.0.0.1 ::1 (static information, in any case) /etc/dnsmasq.conf: server=80.58.61.250 server=80.58.61.254 server=2a02:9000::aaaa server=2a02:9000::bbbb or make "resolv-file=..." point to a file that contains this and doesn't change needlessly: nameserver 80.58.61.250 nameserver 80.58.61.254 nameserver 2a02:9000::aaaa nameserver 2a02:9000::bbbb (can be dynamic information) To achieve the above, I need this /etc/sysconfig/network/config: NETCONFIG_DNS_POLICY='STATIC' NETCONFIG_DNS_FORWARDER='dnsmasq' NETCONFIG_DNS_STATIC_SEARCHLIST='valinor' NETCONFIG_DNS_STATIC_SERVERS='127.0.0.1 ::1' NETCONFIG_DNS_FORWARDER_FALLBACK="yes" It *has* to be done this way or it doesn't work properly. I have tested in many different manners, and this is the best. WHY? /etc/resolv.conf must point only to the local dnsmasq service. It must not be allowed to point to external servers, because that means that programs (say firefox) may bypass dnsmasq and waste time waiting for the remote server to answer. On the other hand, dnsmasq must know about the external servers, it is its job. This can be a static definition, as I am doing right now, or a dynamic definition in some external file, which is what it had. I can not point dnsmasq to an external file that is written every minute, because this causes dnsmasq to reload every minute, cause activity, and spam the logs. So, I consider the dnsmasq issue solved and closed. And thankyou everybody for helping me with ideas finding out what was going on. :-) The only remaining issue is finding out why the router sends advertisements that causes Linux to rewrite the "/run/wicked/leaseinfo.eth0.auto.ipv6" to be written every minute, despite nothing apparently changing. It could be a Linux problem, linux overreacting to the router adverts. I know nothing about this. >>>> But those messages, if they are the ones I remember, do not happen >>>> in my machine. >>> >>> If you are running wicked, they should. >> >> Tell me what string to search for, and I will. > > Ummm, "wicked" :-) > https://paste.opensuse.org/pastes/f5714a73b9ca > > Of course, maybe the difference is that I am running dhcpv6, I don't > really know. I have no messages at all mentioning dhcp in my output, except "Starting wicked DHCPv6 supplicant service..." the first day, so I am using the same as you. journalctl -b | grep wicked | susepaste -n "Carlos E R" -t "wicked journal" -e 40320 <https://paste.opensuse.org/pastes/a13b58a46063> See for yourself, no messages about the lease since boot. >>>>>>> What about /run/dnsmasq-forwarders.conf ? >>>>>> >>>>>> The Beta machine doesn't have dnsmasq. >>>>> >>>>> So install it. That's what I did earlier, to test. >>>> >>>> It would be easier to boot the Laicolasse partition, but that would >>>> break another unrelated test that I'm doing. >>> >>> What can be easier than "zypper in dnsmasq" ? >> >> And configure a few files. No, thanks. I want that machine simple. >> >>>> I try to keep the Beta partition simple. Configuring dnsmasq would >>>> be a further complication. >>> >>> I did not say "configure it", I said _install_ it. When you are done >>> debugging, maybe you could just delete it again. >> >> It has to be configured or it will not work. > > I have to wonder, when you always know better, why do you ask here? Per, please. I have to do the steps I carefully described above to make it work properly. I have now booted to the stable partition in the laptop (Laicolasse) to obtain the information you asked about. The current configuration is (using NM and dnsmasq): cer@Laicolasse:~> grep "NETCONFIG_DNS_STATIC_SEARCHLIST\|NETCONFIG_DNS_STATIC_SERVERS\|NETCONFIG_DNS_FORWARDER\|NETCONFIG_DNS_POLICY" /etc/sysconfig/network/config | egrep -v "^[[:space:]]*$|^#" NETCONFIG_DNS_POLICY="STATIC" NETCONFIG_DNS_FORWARDER="dnsmasq" NETCONFIG_DNS_FORWARDER_FALLBACK="yes" NETCONFIG_DNS_STATIC_SEARCHLIST="valinor" NETCONFIG_DNS_STATIC_SERVERS="127.0.0.1" cer@Laicolasse:~> grep resolv-file /etc/dnsmasq.conf resolv-file=/run/NetworkManager/no-stub-resolv.conf cer@Laicolasse:~> egrep -v "^[[:space:]]*$|^#" /run/NetworkManager/no-stub-resolv.conf search Laicolasse.valinor nameserver 80.58.61.254 nameserver 80.58.61.250 nameserver 2a02:9000::aaaa nameserver 2a02:9000::bbbb cer@Laicolasse:~> egrep -v "^[[:space:]]*$|^#" /etc/resolv.conf search valinor nameserver 127.0.0.1 cer@Laicolasse:~> The file with the external servers doesn't change: cer@Laicolasse:~> l /run/NetworkManager/no-stub-resolv.conf /etc/resolv.conf /run/netconfig/resolv.conf ; date lrwxrwxrwx 1 root root 26 Mar 28 02:36 /etc/resolv.conf -> /run/netconfig/resolv.conf -rw-r--r-- 1 root root 637 May 9 13:35 /run/netconfig/resolv.conf -rw-r--r-- 1 root root 279 May 9 13:35 /run/NetworkManager/no-stub-resolv.conf 2023-05-09T14:15:01 CEST cer@Laicolasse:~> And the file you asked about: cer@Laicolasse:~> l /run/dnsmasq-forwarders.conf -rw-r--r-- 1 root root 556 May 9 13:35 /run/dnsmasq-forwarders.conf cer@Laicolasse:~> It is empty, comments only: cer@Laicolasse:~> egrep -v "^[[:space:]]*$|^#" /run/dnsmasq-forwarders.conf cer@Laicolasse:~> Which to me means the fault is not my router, but Linux, ie, wicked. NM works properly. - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHkEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZFo8tBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVxqwAl2eYIipTCJBYr2lpxC6V J7ZmEOkAnRosa/4qvUJZXRSvW0tuT/RcMvZm =KS5s -----END PGP SIGNATURE-----

3 24

Sigh ..... (was about DNS settings changing too fast)
by Per Jessen 09 May '23

09 May '23

Andrei Borzenkov wrote: > On 09.05.2023 21:28, Carlos E. R. wrote: >> >> In case you missed it, I only want 127.0.0.1 [in /etc/resolv.conf] > > Sigh ... no, I did not miss it. You were told from the very beginning > (not the beginning of *this* thread but some other on the same topic > you started earlier) to edit /etc/resolv.conf and put there whatever > static information you needed. You refused. Which is yet another > reason for my overreaction recently. I too have had to be very careful with not overreacting. I cannot help but think this thread is an archetypical example of how _not_ to ask for support. "I want this problem solved, in this particlarly way, and it doesn't work, help me.". Proposed solutions are refused because "they are not what I want". The much-too-frequently changing DNS config is however a puzzling issue, even if only because it causes too much written to the log. Sofar we have neither explanation nor solution. -- Per Jessen, Zürich (14.8°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

2 1

systemd timers and MAILTO ?
by Per Jessen 08 May '23

08 May '23

I was just working on a new logrotate setup (and expecting to get some error output) when I realised systemd timers don't have any MAILTO option, like cron does. Having googled it a bit, I see some concoctions involving OnFailure scripts, but is that currently the best/only solution? -- Per Jessen, Zürich (20.9°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

6 25

Semi-OT - IP Cam surveillance software, Linux preferred.
by joe a 06 May '23

06 May '23

Since this appears to be a group with persons of many interests, I am searching for a program, along the lines of Blue Iris (windows) or ISpy (multi platform) to monitor perhaps 5 IP Video Cameras. The typical set of features would be necessary, such as, motion detection, zoning, alerts, and so on. I realize there are other forums specific to the topic, but, they sometimes have unspoken bias. I would naturally prefer something that ran natively on Linux and just attempted to compile ISpy on Leap 15.4 (on a VM) but it seemed to take forever to progress, so cut it short to solicit comments here. Delete if deemed inappropriate.

7 12

Make OS read-only
by Roger Oberholtzer 03 May '23

03 May '23

I have Leap on a Raspberry PI. I think my question, however, is generic to all Leaps. I would like to make the OS image read-only, with any changes being in RAM and discarded when the system is restarted. I have seen things where people collect all the writable files to a RAM disk and then replace them in the OS with symbolic links to the RAM disk. While doable, this seems like a fragile way to do this. Is it possible to change how the existing file systems are mounted (/etc/fstab), and add a RAM file system that gets all the changes? All my Googling gets things about when the file system is read-only and it should not be. I want to go the other way. I see that MicroOS's root is read-only. But I do not want the transactions. I want nothing to survive a restart. Except the original read-only stuff. -- Roger Oberholtzer

4 6