tntnet init script always checks for open port 80

Bug #318599 reported by moormaster on 2009-01-18
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tntnet (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: tntnet

I am using Ubuntu intrepid and tried to install and run tntnet 1.6.3-3build1

I have set the listening address and port in the tntnet.conf to 0.0.0.0 85 and cannot start the tntnet daemon using the /etc/init.d/tntnet script because it always checks if port 80 is not in use. There is an apache process listening on port 80 in my case:

  root@localhost:/home/user# /etc/init.d/tntnet start
  Starting tntnet: failed, socket in use.

The init script of Apache for example does not check if a specific port is in use. It just looks for instances of apache in the process list and starts apache if no instance was running. Maybe this could be used as a suggestion to fix this :D

martin suc (martin-suc) wrote :

old post but apparently not fixed

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers