When installing SWAT no connection to localhost:901 possible

Bug #38977 reported by casualprogrammer
28
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

After installing SWAT ( apt-get install swat ) and editing the file /etc/inetd.conf "unable to connect" on localhost:901 or 127.0.0.1:901 occur.

Reason: neither inetd nor xinetd are installed.

There should be a dependency-check for the SWAT package, so that either inetd or xinetd get installed with it and configured properly. (preferably xinetd)

This is affecting:
cat /etc/issue
Ubuntu 6.06 "Dapper Drake" Development Branch \n \l
uname -a
Linux WORKSTATION3U6 2.6.15-20-686 #1 SMP PREEMPT Tue Apr 4 18:37:00 UTC 2006 i686 GNU/Linux

description: updated
Revision history for this message
Frank Niedermann (fbn) wrote :

I have the same issue, confirmed the bug report

Changed in samba:
status: Unconfirmed → Confirmed
Revision history for this message
Brandon Holtsclaw (imbrandon) wrote :

confermed on a clean install and apt-get dist-upgrade

Revision history for this message
olavl (olavl) wrote :

Just confirming the bug.

Revision history for this message
Mark Robinson (launchpad-zl2tod) wrote :

When addressing this bug it may be worth considering adding a
    "Recommends: inetutils-inetd|xinetd" (can't trust that syntax)
to samba too as it puts the following line into /etc/inetd.conf when no inetd is installed:

#<off># netbios-ssn stream tcp nowait root /usr/sbin/tcpd /usr/sbin/smbd

Please note also the file in duplicate bug #50642 which may be worth including in the package for those who elect to use xinetd instead of inetutils-inetd.

Revision history for this message
Chuck Short (zulcss) wrote :

This already been added for hardy.

Thanks
chuck

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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