On Thu, Feb 16, 2012 at 10:13:26AM +0100, Bernd Zeimetz wrote:
> On 02/16/2012 12:22 AM, Serafeim Zanikolas wrote:
> > hi Goswin,
> >
> > On Wed, Feb 15, 2012 at 02:27:48PM +0100, Goswin von Brederlow wrote
> > [edited]:
> >> One thing though: Can I add my own local fragments? Is there a fragment
On Thu, Feb 16, 2012 at 09:41:40AM +0100, Goswin von Brederlow wrote [edited]:
[..]
> Putting local config into /usr/share is wrong though.
the answer to all local policy questions is: like you always did; you edit
inetd.conf.
/usr/share/reconf-inetd fragments are input to a *maintainer* tool. yo
On 02/16/2012 12:22 AM, Serafeim Zanikolas wrote:
> hi Goswin,
>
> On Wed, Feb 15, 2012 at 02:27:48PM +0100, Goswin von Brederlow wrote [edited]:
>> One thing though: Can I add my own local fragments? Is there a fragment
>> dir in /etc for that?
>
> you can, and they should also go to /usr/share/
Serafeim Zanikolas writes:
> hi Goswin,
>
> On Wed, Feb 15, 2012 at 02:27:48PM +0100, Goswin von Brederlow wrote [edited]:
>> One thing though: Can I add my own local fragments? Is there a fragment
>> dir in /etc for that?
>
> you can, and they should also go to /usr/share/reconf-inetd (as long a
hi Goswin,
On Wed, Feb 15, 2012 at 02:27:48PM +0100, Goswin von Brederlow wrote [edited]:
> One thing though: Can I add my own local fragments? Is there a fragment
> dir in /etc for that?
you can, and they should also go to /usr/share/reconf-inetd (as long as the
filenames don't conflict with any
Ian Jackson writes:
> Serafeim Zanikolas writes ("Re: [DEP9] call for testing of reconf-inetd
> (update-inetd replacement)"):
>> Any local sysadmin changes must be done in inetd.conf, as always.
>>
>> The choice of /usr/share/ follows from two of the r
Serafeim Zanikolas writes ("Re: [DEP9] call for testing of reconf-inetd
(update-inetd replacement)"):
> Any local sysadmin changes must be done in inetd.conf, as always.
>
> The choice of /usr/share/ follows from two of the requirements I
> have set from the beginning fo
Hi Ian,
First of all, thanks for the feedback.
On Mon, Feb 13, 2012 at 12:36:40PM +, Ian Jackson wrote:
> Serafeim Zanikolas writes ("[DEP9] call for testing of reconf-inetd
> (update-inetd replacement)"):
> > To test it, in a nutshell:
> >
> > - make
Serafeim Zanikolas writes ("[DEP9] call for testing of reconf-inetd
(update-inetd replacement)"):
> To test it, in a nutshell:
>
> - make your package install xinetd.conf(5) fragment files in
> /usr/share/reconf-inetd/, one file per service that needs an entry
Hi,
reconf-inetd is the replacement of update-inetd, as per DEP9. Unlike past
proposals for replacing update-inetd, this one is actually implemented and
available in experimental.
This should be of interest for services that
- require separate inetd.conf entries for ipv4/ipv6 versions
-
10 matches
Mail list logo
