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

Michael Holzt wrote:
 > I have no knowledge about xinetd, but i guess there is a generic way in
> xinetd to tell it the port. Don't you have any other services in xinetd
> and can lookup how its done there?
> 
>> 4. Well, xinetd seems to be out of favor anyway, and this link
>> http://wiki.qpsmtpd.org/inetd?DokuWiki=9f8ba8fcd90e3c53f6a715c256a51775&do=revisions
>> shows that there used to be an xinetd page in the wiki, but it was moved two 
>> weeks ago by jamtur01, and since then it has vanished.
> 
> The last revision of the page can be seen here:
> http://wiki.qpsmtpd.org/deploy:inetd?rev=1168341647
> 

See http://wiki.qpsmtpd.org/deploy:start

I talks about x(inetd) and links to the patch provided to fix it at 0.32.

Linked off the main page start page.

Regards

James Turnbull

- --
James Turnbull <[EMAIL PROTECTED]>
- ---
Author of Pro Nagios 2.0
(http://www.amazon.com/gp/product/1590596099/)

Hardening Linux
(http://www.amazon.com/gp/product/1590594444/)
- ---
PGP Key (http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x0C42DF40)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFtkUx9hTGvAxC30ARAl8KAJ4tyb8nmgdu5RONPPEVPmbmHsjRpACgkd07
4xbLSUA6BP0F4uRImw0lPcQ=
=tMvD
-----END PGP SIGNATURE-----

Reply via email to