Your message dated Mon, 4 Jan 2010 22:48:50 +0100
with message-id <[email protected]>
and subject line Package removed from Debian unstable
has caused the Debian Bug report #368643,
regarding gidentd: conflicts with bind9: localhost inetd[pid]: auth/tcp: bind: 
Address already in use
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
368643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368643
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gidentd
Version: 0.4.5-7.1
Severity: normal


when running gidentd and bind9 together (with bind9 in default config), 
I get "localhost inetd[3985]: auth/tcp: bind: Address already in use" 
errors.

Running bidentd instead of gidentd solved this problem. (I needed an 
identd for postgresql-8.1 automatic startup on boot).

Regards...

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-686
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)

Versions of packages gidentd depends on:
ii  debconf                       1.5.1      Debian configuration management sy
ii  libc6                         2.3.6-9    GNU C Library: Shared libraries

gidentd recommends no packages.


--- End Message ---
--- Begin Message ---
Version: 0.4.5+dfsg1-0.2+rm

Package removed from Debian unstable: http://bugs.debian.org/563580

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


--- End Message ---

Reply via email to