Bug#844086: lxc: On "sysv-init", fail to initialize cgroup since "cgmanager" support dropped.

2017-01-11 Thread Thibaut Chèze
Hi, I reopen this because I have seen another side effect. The LXC containers fail to start automatically during boot. I attach a patch to fix this. I haven't tested with "systemd" as "init", but I think it's not a problem ("systemd" doesn't use /etc/init.d/lxc script, right ?). Best regards, -

Bug#844086: lxc: On "sysv-init", fail to initialize cgroup since "cgmanager" support dropped.

2016-11-12 Thread Thibaut Chèze
Package: lxc Version: 1:2.0.5-3 Severity: important Tags: newcomer Found: 1:2.0.5-1 Notfound: 1:2.0.4-1 Hi, After an upgrade from /1:2.0.4-1/, lxc containers fails to start on /SysV init/. It seems that it is following the removal of "cgmanager" support. A workaround is to install the "cgroupfs

Bug#808470: samhain: Reload affects all instances, not only the one in //run/samhain/samhain.pid/.

2016-03-14 Thread Thibaut Chèze
Hi, With my previous patches, I have forgotten 2 modifications of running() function: - The output of the pid found - The check for instance without PIDFILE. The attached patch contains all modifications without cleaning spaces/indent. Regards, diff -ru samhain-3.1.0/debian/samhain.init samha

Bug#817841: openresolv: doesn't work with multiple domains in search, they are concatenated.

2016-03-12 Thread Thibaut Chèze
Ticket available on: http://roy.marples.name/projects/openresolv/tktview/2557e09a73327a41b2cc6676bacf42966f53df35 signature.asc Description: OpenPGP digital signature

Bug#817841: openresolv: doesn't work with multiple domains in search, they are concatenated.

2016-03-10 Thread Thibaut Chèze
Package: openresolv Version: 3.7.3-1 Severity: important Tags: upstream Hi, The problem occurs since the new /3.7.3-1/. A way to reproduce (using bind): # resolvconf -a wlan0 < domain test2.example.org > search test2.example.org. example.org. test1.example.org > nameserver 192.168.0.1 > EOF Fai

Bug#808470: samhain: Reload affects all instances, not only the one in //run/samhain/samhain.pid/.

2016-02-13 Thread Thibaut Chèze
Hi, With my previous patch, the waiting time of the stop action is sometimes insufficient. For information on my systems, the time has never exceeded 7 seconds. The second patch (samhain-reindent.patch) is cleaning spaces/indent, if you want it. Regards, diff -ru samhain-3.1.0-patched/debian/sam

Bug#808470: samhain: Reload affects all instances, not only the one in //run/samhain/samhain.pid/.

2015-12-20 Thread Thibaut Chèze
Package: samhain Version: 3.1.0-7 Severity: minor Tags: patch The problem affects manually started instances and instances inside /lxc/'s containers (if /samhain/ is installed on host and guests) when the log rotation occurs on host. The patch have an other side effect: the child process isn't ki

Bug#807808: openvpn: Please preserve order of pushed parameters in update-resolv-conf, if more than 9.

2015-12-13 Thread Thibaut Chèze
Package: openvpn Version: 2.3.7-2+b1 Severity: minor Tags: patch Hi, I came across a bug when using /update-resolv-conf/ in my configuration. Indeed, when there are more than 9 parameters pushed from the server, the order isn't kept, when applied. Here's my patch to fix this problem. Best regar

Bug#799041: Updated rules for isc-dhcp-server.

2015-12-08 Thread Thibaut Chèze
Hi, Thank you. In case you are interrested, here's my patch for it. He keeps working with previous versions of /isc-dhcp-server/. Best regards, --- logcheck-1.3.17/rulefiles/linux/ignore.d.server/dhcp 2014-10-25 00:01:52.0 +0200 +++ logcheck-1.3.17-patched/rulefiles/linux/ignore.d.server

Bug#792430: openresolv: Fail if a zone is declared on multiple interfaces.

2015-12-01 Thread Thibaut Chèze
inion, we should only have access to one zone at a time, the one provided by the highest priority interface for example. However, it would be useful to keep the fusion for resolvers on the same interface, provided by different sources like DHCP and DHCPv6... What do you think ? Best regards,

Bug#792428: openresolv: "Failed to get D-Bus connection" randomly at update and boot on bind9 restart

2015-12-01 Thread Thibaut Chèze
.5.2-1/ seems to use the init script in //etc/init.d/ instead. Best regards, Thibaut Chèze signature.asc Description: OpenPGP digital signature

Bug#798237: (no subject)

2015-09-20 Thread Thibaut Chèze
I rolled back to the previous version /4.3.3-1/ using packages from /snapshot.debian.org/, and it's working perfectly (with 'interim', didn't try for 'standard' yet). I think, the problem doesn't come from the sources but from compilation options. Best regard

Bug#792428: openresolv: "Failed to get D-Bus connection" randomly at update and boot on bind9 restart

2015-07-14 Thread Thibaut Chèze
My workaround for this problem is to stay in version /3.5.2-1/. Le 14/07/2015 19:48, Thibaut Chèze wrote : > Package: openresolv > Version: 3.7.0-1 > Severity: normal > Tags: upstream > > > After an update from any source (dhcp, openvpn, static, ...), restart of > bind fai

Bug#792430: openresolv: Fail if a zone is declared on multiple interfaces.

2015-07-14 Thread Thibaut Chèze
perfect, but technically, the problem have no solution (if zones are the same, it works perfectly, else, some zone are not reachable). This problem also affects the version /3.5.2-1/. Best regards, Thibaut Chèze -- System Information: Debian Release: stretch/sid APT prefers testing-proposed-u

Bug#792428: openresolv: "Failed to get D-Bus connection" randomly at update and boot on bind9 restart

2015-07-14 Thread Thibaut Chèze
Package: openresolv Version: 3.7.0-1 Severity: normal Tags: upstream After an update from any source (dhcp, openvpn, static, ...), restart of bind fail with message: Failed to get D-Bus connection: Operation not permitted It's not all the time, but very very often. Best regards, Thibaut