Bug#807428: [Debian-ha-maintainers] Bug#807428: Bug#807428: csync2: socket activation and running as system user

2016-10-16 Thread Christoph Berg
Re: Valentin Vidic 2016-10-16 <20161016081037.btwvht6ol4ro2...@gavran.carpriv.carnet.hr> > On Wed, Jun 22, 2016 at 09:39:22AM +0200, Christoph Berg wrote: > > Don't get me wrong, I would also like to see it handled via systemd, > > but at the moment I think it would cause more trouble than it woul

Bug#807428: [Debian-ha-maintainers] Bug#807428: Bug#807428: csync2: socket activation and running as system user

2016-10-16 Thread Valentin Vidic
On Wed, Jun 22, 2016 at 09:39:22AM +0200, Christoph Berg wrote: > Don't get me wrong, I would also like to see it handled via systemd, > but at the moment I think it would cause more trouble than it would > solve. What if we move inetd to recommends and ship systemd service in disabled state? It

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

2016-07-26 Thread Dhionel Díaz
El 22/06/16 a las 09:00, Dhionel Díaz escribió: > El 21/06/16 a las 16:36, Ferenc Wágner escribió: >> Christoph Berg writes: >> >>> Re: Dhionel Díaz 2016-06-21 >>> <0c44f8f5-4d46-60e7-2bc3-d16956869...@cenditel.gob.ve> >>> > What about depending on inetd | systemd-sysv and invoking update-ine

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

2016-06-22 Thread Dhionel Díaz
El 21/06/16 a las 16:36, Ferenc Wágner escribió: > Christoph Berg writes: > >> Re: Dhionel Díaz 2016-06-21 >> <0c44f8f5-4d46-60e7-2bc3-d16956869...@cenditel.gob.ve> >> What about depending on inetd | systemd-sysv and invoking update-inetd only if systemd is not running? >> >> Doesn't t

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

2016-06-22 Thread Christoph Berg
Re: Ferenc Wágner 2016-06-22 <87vb111z5s@lant.ki.iif.hu> > Inefficient more in the administrative sense: you're running the daemon > via inetd (started by systemd) instead of running the daemon directly > from systemd. But I'm not even sure this idea is feasible, as the > conflicting units wou

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

2016-06-22 Thread Ferenc Wágner
Christoph Berg writes: > Re: Ferenc Wágner 2016-06-21 <87eg7q2s9s@lant.ki.iif.hu> > >> Hmm, maybe you could have the csync2.socket conflict with inet.service >> to avoid this failure mode... That would serve csync2 via inetd instead >> of systemd, which is inefficient, but maybe acceptable.

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

2016-06-21 Thread Christoph Berg
Re: Ferenc Wágner 2016-06-21 <87eg7q2s9s@lant.ki.iif.hu> > Christoph Berg writes: > > > Re: Dhionel Díaz 2016-06-21 > > <0c44f8f5-4d46-60e7-2bc3-d16956869...@cenditel.gob.ve> > > > >>> What about depending on inetd | systemd-sysv and invoking update-inetd > >>> only if systemd is not running

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

2016-06-21 Thread Ferenc Wágner
Christoph Berg writes: > Re: Dhionel Díaz 2016-06-21 > <0c44f8f5-4d46-60e7-2bc3-d16956869...@cenditel.gob.ve> > >>> What about depending on inetd | systemd-sysv and invoking update-inetd >>> only if systemd is not running? > > Doesn't that fail if the system is switched to/from systemd after the

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

2016-06-21 Thread Christoph Berg
Re: Dhionel Díaz 2016-06-21 <0c44f8f5-4d46-60e7-2bc3-d16956869...@cenditel.gob.ve> > > What about depending on inetd | systemd-sysv and invoking update-inetd > > only if systemd is not running? Doesn't that fail if the system is switched to/from systemd after the package was already installed? >

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

2016-06-21 Thread Dhionel Díaz
El 21/06/16 a las 02:15, Ferenc Wágner escribió: > Dhionel Díaz writes: > >> El 20/06/16 a las 05:57, Christoph Berg escribió: >> >>> Re: Dhionel Díaz 2015-12-08 <5667290f.3060...@cenditel.gob.ve> >>> The attached patch was prepared to make csync2 a socket activated service managed with

Bug#807428: [Debian-ha-maintainers] Bug#807428: csync2: socket activation and running as system user

2016-06-20 Thread Ferenc Wágner
Dhionel Díaz writes: > El 20/06/16 a las 05:57, Christoph Berg escribió: > >> Re: Dhionel Díaz 2015-12-08 <5667290f.3060...@cenditel.gob.ve> >> >>> The attached patch was prepared to make csync2 a socket activated >>> service managed with systemd and avoid the use of inetd, >> >> Unfortunately

Bug#807428: csync2: socket activation and running as system user

2016-06-20 Thread Dhionel Díaz
El 20/06/16 a las 05:57, Christoph Berg escribió: > Control: tags -1 -patch > > Re: Dhionel Díaz 2015-12-08 <5667290f.3060...@cenditel.gob.ve> >> The attached patch was prepared to make csync2 a socket activated >> service managed with systemd and avoid the use of inetd, > > Hi Dhionel, > > than

Bug#807428: csync2: socket activation and running as system user

2016-06-20 Thread Christoph Berg
Control: tags -1 -patch Re: Dhionel Díaz 2015-12-08 <5667290f.3060...@cenditel.gob.ve> > The attached patch was prepared to make csync2 a socket activated > service managed with systemd and avoid the use of inetd, Hi Dhionel, thanks for the patch. Unfortunately I don't think we should apply it

Bug#807428: csync2: socket activation and running as system user

2015-12-08 Thread Dhionel Díaz
Package: csync2 Version: 2.0+73d3293-2 Severity: wishlist Tags: patch Usertags: systemd-units X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org Dear Maintainer, The attached patch was prepared to make csync2 a socket activated service managed with systemd and avoid the use of inetd, i