ferm: suggested systemd unit file

2015-10-20 Thread Sam Morris
40-systemd and documented in sd_booted(3). Or you could just drop DISABLED which is not even necessary under sysvinit: 'update-rc.d ferm disable' should work just fine for those that don't want to rename the symlink in /etc/rcS.d themselves. -- Sam Morris <https://robots.o

Re: ferm: suggested systemd unit file

2015-10-20 Thread Sam Morris
On Tue, 2015-10-20 at 12:34 -0300, Felipe Sateler wrote: > On 20 October 2015 at 10:23, Sam Morris wrote: > > I just ran into this: Ferm was not started at boot. Running > > 'journalctl > > -b' revealed the following: > > > > Oct 20 13:18:37

Re: ferm: suggested systemd unit file

2015-10-20 Thread Sam Morris
> The problem is that at network-pre.target time the interfaces may not > even exist, if the interfaces are not physical (eg, bridges are set up > by networkd or ifupdown, which are After=network-pre.target). It's OK for firewall rules to reference interfaces that don't exis

Bug#812522: Disable systemd-timesyncd in VirtualBox guests

2016-01-24 Thread Sam Morris
Package: systemd Version: 228-4 Severity: wishlist File: /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The 'virtualbox-guest-utils' service provides time synchronization with the host when run inside VirtualBox. It mig

Bug#816612: systemd: Assertion failure, systemd stopped responding

2016-03-03 Thread Sam Morris
Package: systemd Version: 229-2 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Installing an unrelated package failed: # apt install iptables-nftables-compat Reading package lists... Done Building dependency tree Reading state informati

Bug#816612: systemd: Assertion failure, systemd stopped responding

2016-03-04 Thread Sam Morris
On Thu, 2016-03-03 at 19:26 +0100, Michael Biebl wrote: > Am 03.03.2016 um 14:47 schrieb Sam Morris: > > > > Package: systemd > > Version: 229-2 > > Severity: important > > > > systemd seems to have stopped reponding to requests. The journal > > cont

lintian: warn when (systemd) service units install themselves into an unusual target

2016-03-09 Thread Sam Morris
$unit" | grep ^WantedBy=); for x in $w; do printf '%s %s\n' $x "$unit"; done; done and the false positives were from systemd itself, bluez and anacron. -- Sam Morris <https://robots.org.uk/> CAAA AA1A CA69 A83A 892B 1855 D20B 4202 5CDA 27B9 >From 13fe1c75dae2d64d61

Bug#817998: /lib/x86_64-linux-gnu/libsystemd.so.0: sd_pid_get_session incorrectly(?) returning -ENXIO (sesion does not exist)

2016-03-12 Thread Sam Morris
Package: libsystemd0 Version: 229-2 Severity: normal File: /lib/x86_64-linux-gnu/libsystemd.so.0 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I'm trying to work out why I get the following: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1 (polkit-gnome-authentic

Bug#817998: /lib/x86_64-linux-gnu/libsystemd.so.0: sd_pid_get_session incorrectly(?) returning -ENXIO (sesion does not exist)

2016-03-13 Thread Sam Morris
thanks This is caused by gnome-terminal's design of spawning all child processes via gnome-terminal-server which is spawned from the user's dbus session. For a 'fun' reproduction, launch nm-connection-editor from gnome- terminal and try to figure out why it doesn't work.

Bug#826045: systemd: Suggested kernel/initramfs-tools integration scripts

2017-10-18 Thread Sam Morris
Package: systemd Version: 232-25+deb9u1 Tags: + patch Followup-For: Bug #826045 -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Here are the scripts I've been using. I've arranged for the initramfs post-update script to run kernel-install in the usual case; the kernel postinst script will only do

Re: Bug#744753: anacron: Anacron not triggered when system resumes under systemd

2014-06-04 Thread Sam Morris
exits. It's intended as a replacement for the daily/weekly/monthly cron jobs, which will not run if your computer is turned off when their time arrives. > > Lennart > -- Sam Morris <https://robots.org.uk/> 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 _

Bug#753576: systemd stopped responding to dbus.socket connections

2014-07-03 Thread Sam Morris
Package: systemd Version: 204-8~bpo70+1 Severity: normal My desktop has been up for 31 days. Today I noticed I could no longer connect to the system dbus daemon. I'll leave the system up

Bug#753576: systemd stopped responding to dbus.socket connections

2014-07-03 Thread Sam Morris
A unix -lnp | grep dbus unix 2 [ ACC ] STREAM LISTENING 7809 1/systemd /var/run/dbus/system_bus_socket > Does strace -p 1124 reveal anything useful? I ran strace on both dbus and systemd. Both remain sleeping epoll_wait during the attempt to connect to the socket.

Bug#753576: systemd stopped responding to dbus.socket connections

2014-07-03 Thread Sam Morris
On Thu, Jul 03, 2014 at 01:35:59PM +0200, Michael Biebl wrote: > Am 03.07.2014 13:03, schrieb Sam Morris: > > On Thu, Jul 03, 2014 at 12:30:14PM +0200, Michael Biebl wrote: > >> If dbus is running (and it apparently is), then it should be the process > >>