On Apr 13, Raphael Hertzog wrote:
> Consistency between package name and init script and service file
> has no reason to be classified as "historical accident", it seems
> to be nice bonus point to me...
I think that consistenct between daemon name and systemd unit name is
a much better goal.
-
On Thu, 13 Apr 2017, Marco d'Itri wrote:
> On Apr 11, Raphael Hertzog wrote:
>
> > Why aren't you providing openbsd-inetd.service as the real file and
> > inetd.service as a symlink ?
> Because naming the init script "openbsd-inetd" was an historical
> accident caused by problems when replacing
On Apr 11, Raphael Hertzog wrote:
> Why aren't you providing openbsd-inetd.service as the real file and
> inetd.service as a symlink ?
Because naming the init script "openbsd-inetd" was an historical
accident caused by problems when replacing the old netkit-inetd.
Since we had this in jessie and
Am 11.04.2017 um 19:17 schrieb Michael Biebl:
> Renaming the .service file so the SysV init script and systemd service
> unit name align is a valid solution for this particular case. But then
> again, we have other packages where the names don't align.
That said, my recommendation is still that th
Am 11.04.2017 um 18:01 schrieb Raphael Hertzog:
> On Tue, 11 Apr 2017, Marco d'Itri wrote:
>> On Apr 11, Niels Thykier wrote:
>>
>>> Are there any updates on this bug? If not, then we will be inclined to
>> I do not think that there is anything I can or should do in
>> openbsd-inetd: the bug sho
On Tue, 11 Apr 2017, Marco d'Itri wrote:
> On Apr 11, Niels Thykier wrote:
>
> > Are there any updates on this bug? If not, then we will be inclined to
> I do not think that there is anything I can or should do in
> openbsd-inetd: the bug should either be closed or downgraded.
Why aren't you p
On Apr 11, Niels Thykier wrote:
> Are there any updates on this bug? If not, then we will be inclined to
I do not think that there is anything I can or should do in
openbsd-inetd: the bug should either be closed or downgraded.
> remove openbsd-inetd from testing.
Bad idea, since it is our "goo
On Tue, 3 Jan 2017 09:59:10 +0100 Raphael Hertzog
wrote:
> Hi Marco,
>
> On Mon, 26 Dec 2016, Marco d'Itri wrote:
> > On Apr 10, Michael Biebl wrote:
> >
> > > Ideally, the .service file name and sysv init script do match.
> > > If that is not the case, because upstream chose a different name,
Hi Marco,
On Mon, 26 Dec 2016, Marco d'Itri wrote:
> On Apr 10, Michael Biebl wrote:
>
> > Ideally, the .service file name and sysv init script do match.
> > If that is not the case, because upstream chose a different name, my
> > recommendation is to create a symlink and ship that statically in
On Apr 10, Michael Biebl wrote:
> Ideally, the .service file name and sysv init script do match.
> If that is not the case, because upstream chose a different name, my
> recommendation is to create a symlink and ship that statically in the
> package, i.e. not create it via Alias=.
Such a link alr
Package: openbsd-inetd
Version: 0.20140418-2
Severity: serious
User: de...@kali.org
Usertags: origin-kali
systemd doesn't seem to handle having two service files for the same
service very well.
For example, "systemctl disable openbsd-inetd" does not work since
inetd.service is the unit enabled by
11 matches
Mail list logo
