Bug#925444: smokeping: --pid-dir doesn't worj as expected

2020-05-02 Thread Cameron Davidson
Hi Gabriel, thanks for getting back to me - the timing was good, because the issue  has just recurred on my system. You are of course correct in what _should_ have happened based on the contents of the unit file. I just jumped to the wrong conclusion based on the error message, and that my

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2020-02-10 Thread Cameron Davidson
This has just started hapenning to my also. The cause, I think, that evenutally a tmpfile cleanup will delete /run/smokeping - maybe depends on age and/or  because it is not owned by root. One solution (I found for other systemd processes run as non-root) is to add a config file:

Bug#925444: smokeping: --pid-dir doesn't worj as expected

2020-02-10 Thread Cameron Davidson
Sorry, a followup to my incomplete previous post... After upgrade from Debian 9 to 10... /run on my system is now mounted on a tmpfs and is therefore recreated empty at reboot.  The old pidfile location /var/run is symlinked to /run. The folder /run/smokeping needs to be recreated each reboot

Bug#932085: grub-common: Grub can't load initrd for Xen after upgrade to Buster

2019-11-08 Thread Cameron Davidson
I also had the same problem after upgrading from 9.9 to 10.1. (from network repos 8 November 2019). The symptoms were the same, on the video console, the message appeared (not verbatim as I forgot to transcribe it)  loading xen-4.11  then the same old warning about no available console for the

Bug#927747: [Pkg-samba-maint] Bug#927747: bind9_dlz backend is entirely broken in Debian

2019-10-24 Thread Cameron Davidson
I would like to add my observations on this bug after upgrading from stretch to 10.1. The apparmor fixes seem OK so far. My samba system was originally created by moving a samba-3 system from CentOS 6 to Debian 9 and then using the samba tools to migrate to an ad-dc system. I mention this,