Fresh installed xinetd does not start

Bug #7876 reported by Debian Bug Importer
4
Affects Status Importance Assigned to Milestone
xinetd (Debian)
Fix Released
Unknown
xinetd (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

Automatically imported from Debian bug report #270803 http://bugs.debian.org/270803

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Automatically imported from Debian bug report #270803 http://bugs.debian.org/270803

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Thu, 09 Sep 2004 13:45:34 +0200
From: Akos Gabriel <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: Fresh installed xinetd does not start

Package: xinetd
Version: 1:2.3.13-1
Severity: grave
Tags: patch
Justification: renders package unusable

I installed base system with inetd, and wanted to switch to xinetd.
I've issued apt-get install xinetd, and wondering why it did not started.
After comparing the actual configuration with an already working one, it
turned out that a file is missing (/etc/xinetd.d/xinetd):

service services
{
        disable = yes
        type = INTERNAL UNLISTED
        bind = 127.0.0.1
        port = 9098
        socket_type = stream
        protocol = tcp
        wait = no
        only_from = 127.0.0.1
}

Regards,
Akos

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-20040907evms1
Locale: LANG=C, LC_CTYPE=C

Versions of packages xinetd depends on:
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii libwrap0 7.6.dbs-5 Wietse Venema's TCP wrappers libra
ii netbase 4.18 Basic TCP/IP networking system

-- no debconf information

Revision history for this message
Matt Zimmerman (mdz) wrote :

xinetd doesn't start by default because no services are configured. This is OK.

Revision history for this message
In , Frank Lichtenheld (djpig) wrote : Re: Bug#270803: Fresh installed xinetd does not start

On Thu, Sep 09, 2004 at 01:45:34PM +0200, Akos Gabriel wrote:
> I installed base system with inetd, and wanted to switch to xinetd.
> I've issued apt-get install xinetd, and wondering why it did not started.
> After comparing the actual configuration with an already working one, it
> turned out that a file is missing (/etc/xinetd.d/xinetd):
>
> service services
> {
> disable = yes
> type = INTERNAL UNLISTED
> bind = 127.0.0.1
> port = 9098
> socket_type = stream
> protocol = tcp
> wait = no
> only_from = 127.0.0.1
> }

I'm a bit confused about this bug. Obviously removing the file
was intended:
<quote changelog enty for 1:2.3.13-1>
"services" internal service was removed upstream, so we don't
need /etc/xinetd.d/xinetd anymore, nor documentation for these
internal services (closes: #242646)
</quote>

As I know nothing about xinetd nor have a spare machine where I could
test it, a comment on the validity of this bug from someone who can
would be appreciated. Maintainer? Other volunteers?

Gruesse,
--
Frank Lichtenheld <email address hidden>
www: http://www.djpig.de/

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 22 Sep 2004 15:53:24 +0200
From: Frank Lichtenheld <email address hidden>
To: Akos Gabriel <email address hidden>, <email address hidden>
Subject: Re: Bug#270803: Fresh installed xinetd does not start

On Thu, Sep 09, 2004 at 01:45:34PM +0200, Akos Gabriel wrote:
> I installed base system with inetd, and wanted to switch to xinetd.
> I've issued apt-get install xinetd, and wondering why it did not started.
> After comparing the actual configuration with an already working one, it
> turned out that a file is missing (/etc/xinetd.d/xinetd):
>
> service services
> {
> disable = yes
> type = INTERNAL UNLISTED
> bind = 127.0.0.1
> port = 9098
> socket_type = stream
> protocol = tcp
> wait = no
> only_from = 127.0.0.1
> }

I'm a bit confused about this bug. Obviously removing the file
was intended:
<quote changelog enty for 1:2.3.13-1>
"services" internal service was removed upstream, so we don't
need /etc/xinetd.d/xinetd anymore, nor documentation for these
internal services (closes: #242646)
</quote>

As I know nothing about xinetd nor have a spare machine where I could
test it, a comment on the validity of this bug from someone who can
would be appreciated. Maintainer? Other volunteers?

Gruesse,
--
Frank Lichtenheld <email address hidden>
www: http://www.djpig.de/

Revision history for this message
In , Thomas Seyrat (tomasera) wrote :

  Hi,

On September 22, 15:53 (+0200), Frank Lichtenheld wrote:
> I'm a bit confused about this bug. Obviously removing the file
> was intended:
[...]
> As I know nothing about xinetd nor have a spare machine where I could
> test it, a comment on the validity of this bug from someone who can
> would be appreciated. Maintainer? Other volunteers?

  Indeed removing the file was intended. The fact is, xinetd's present
  behaviour is not to start if no service is enabled. This may not be a
  good thing, after all. I will upload xinetd 1:2.3.13-2, with an init
  script that starts xinetd with the -stayalive option, and this way
  allows it to keep running even with no enabled service.

  Thanks, cheers,

--
Thomas Seyrat

Revision history for this message
In , Thomas Seyrat (tomasera) wrote : Bug#270803: fixed in xinetd 1:2.3.13-2

Source: xinetd
Source-Version: 1:2.3.13-2

We believe that the bug you reported is fixed in the latest version of
xinetd, which is due to be installed in the Debian FTP archive:

xinetd_2.3.13-2.diff.gz
  to pool/main/x/xinetd/xinetd_2.3.13-2.diff.gz
xinetd_2.3.13-2.dsc
  to pool/main/x/xinetd/xinetd_2.3.13-2.dsc
xinetd_2.3.13-2_powerpc.deb
  to pool/main/x/xinetd/xinetd_2.3.13-2_powerpc.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Seyrat <email address hidden> (supplier of updated xinetd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 9 Sep 2004 14:39:20 +0200
Source: xinetd
Binary: xinetd
Architecture: source powerpc
Version: 1:2.3.13-2
Distribution: unstable
Urgency: low
Maintainer: Thomas Seyrat <email address hidden>
Changed-By: Thomas Seyrat <email address hidden>
Description:
 xinetd - replacement for inetd with many enhancements
Closes: 270803
Changes:
 xinetd (1:2.3.13-2) unstable; urgency=low
 .
   * We now start xinetd with -stayalive by default to keep it
     running even if no service is enabled. (closes: #270803)
   * Modify Makefile.in to install xinetd.log manpage in section
     5 instead of 8.
Files:
 fab9c418a6bb7f6b67e00294d5d89cf9 579 net extra xinetd_2.3.13-2.dsc
 911c9e43df3b889a73652703b509fffc 12573 net extra xinetd_2.3.13-2.diff.gz
 ede19efe7e9c639fed9e892783e7051a 139394 net extra xinetd_2.3.13-2_powerpc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBUfD4G7q+HrSg3okRApH/AJ9PLPzf7AgHcskPiyH4KcKQ5oNU4gCfZooI
xJawP/pz1sK1HlyCkTIs9MU=
=nLCf
-----END PGP SIGNATURE-----

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Wed, 22 Sep 2004 23:44:50 +0200
From: Thomas Seyrat <email address hidden>
To: Frank Lichtenheld <email address hidden>, <email address hidden>
Cc: Akos Gabriel <email address hidden>
Subject: Re: Bug#270803: Fresh installed xinetd does not start

  Hi,

On September 22, 15:53 (+0200), Frank Lichtenheld wrote:
> I'm a bit confused about this bug. Obviously removing the file
> was intended:
[...]
> As I know nothing about xinetd nor have a spare machine where I could
> test it, a comment on the validity of this bug from someone who can
> would be appreciated. Maintainer? Other volunteers?

  Indeed removing the file was intended. The fact is, xinetd's present
  behaviour is not to start if no service is enabled. This may not be a
  good thing, after all. I will upload xinetd 1:2.3.13-2, with an init
  script that starts xinetd with the -stayalive option, and this way
  allows it to keep running even with no enabled service.

  Thanks, cheers,

--
Thomas Seyrat

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-Id: <email address hidden>
Date: Wed, 22 Sep 2004 18:17:10 -0400
From: Thomas Seyrat <email address hidden>
To: <email address hidden>
Subject: Bug#270803: fixed in xinetd 1:2.3.13-2

Source: xinetd
Source-Version: 1:2.3.13-2

We believe that the bug you reported is fixed in the latest version of
xinetd, which is due to be installed in the Debian FTP archive:

xinetd_2.3.13-2.diff.gz
  to pool/main/x/xinetd/xinetd_2.3.13-2.diff.gz
xinetd_2.3.13-2.dsc
  to pool/main/x/xinetd/xinetd_2.3.13-2.dsc
xinetd_2.3.13-2_powerpc.deb
  to pool/main/x/xinetd/xinetd_2.3.13-2_powerpc.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Seyrat <email address hidden> (supplier of updated xinetd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 9 Sep 2004 14:39:20 +0200
Source: xinetd
Binary: xinetd
Architecture: source powerpc
Version: 1:2.3.13-2
Distribution: unstable
Urgency: low
Maintainer: Thomas Seyrat <email address hidden>
Changed-By: Thomas Seyrat <email address hidden>
Description:
 xinetd - replacement for inetd with many enhancements
Closes: 270803
Changes:
 xinetd (1:2.3.13-2) unstable; urgency=low
 .
   * We now start xinetd with -stayalive by default to keep it
     running even if no service is enabled. (closes: #270803)
   * Modify Makefile.in to install xinetd.log manpage in section
     5 instead of 8.
Files:
 fab9c418a6bb7f6b67e00294d5d89cf9 579 net extra xinetd_2.3.13-2.dsc
 911c9e43df3b889a73652703b509fffc 12573 net extra xinetd_2.3.13-2.diff.gz
 ede19efe7e9c639fed9e892783e7051a 139394 net extra xinetd_2.3.13-2_powerpc.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBUfD4G7q+HrSg3okRApH/AJ9PLPzf7AgHcskPiyH4KcKQ5oNU4gCfZooI
xJawP/pz1sK1HlyCkTIs9MU=
=nLCf
-----END PGP SIGNATURE-----

Revision history for this message
In , Gary Peck (gbpeck) wrote : Re: Bug#270803: Fresh installed xinetd does not start

> Indeed removing the file was intended. The fact is, xinetd's present
> behaviour is not to start if no service is enabled. This may not be a
> good thing, after all.

Why is this not a good thing? There's no reason for xinetd to run if
there's no services configured. This seems completely rational to me.
You might, though, want to change the startup script to not report
success unless xinetd actually started. That way users won't be misled
into thinking that xinetd is running when it's not. Either way, a quick
look in /var/log/syslog would clearly show the reason xinetd did not
start up.

gary

Revision history for this message
Debian Bug Importer (debzilla) wrote :

Message-ID: <email address hidden>
Date: Mon, 4 Oct 2004 14:10:09 -0700
From: Gary Peck <email address hidden>
To: Thomas Seyrat <email address hidden>, <email address hidden>
Cc: Akos Gabriel <email address hidden>
Subject: Re: Bug#270803: Fresh installed xinetd does not start

> Indeed removing the file was intended. The fact is, xinetd's present
> behaviour is not to start if no service is enabled. This may not be a
> good thing, after all.

Why is this not a good thing? There's no reason for xinetd to run if
there's no services configured. This seems completely rational to me.
You might, though, want to change the startup script to not report
success unless xinetd actually started. That way users won't be misled
into thinking that xinetd is running when it's not. Either way, a quick
look in /var/log/syslog would clearly show the reason xinetd did not
start up.

gary

Revision history for this message
Matt Zimmerman (mdz) wrote :

Fixed via import from Debian:

    xinetd | 1:2.3.13-2 | http://archive.ubuntu.com hoary/main Sources

Changed in xinetd:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.