Hello I'm trying to configure imap; I gather it is necessary to have xinetd running first, is this correct? OK, the problem is xinetd refuses to start, it displays this message: # rcxinetd start Starting INET services. (xinetd) failed # I don't have any idea where to look for debug info, or otherwise look for a clue. The system is SUSE 10.0 Thanks in advance. Juan Pablo
Juan Pablo Romero wrote:
Hello
I'm trying to configure imap; I gather it is necessary to have xinetd running first, is this correct?
Not necessarily. Running an imap server through xinetd is one option, but I think running it as a stand-alone daemon is probably better. I tend to use xinetd for on-demand, but infrequently used services.
OK, the problem is xinetd refuses to start, it displays this message:
# rcxinetd start Starting INET services. (xinetd) failed #
Have you configured the services that you wish xinetd to provide? I suspect it might fail to start if it hasn't got any services to offer. Check /etc/xinet.d/ and /etc/xinetd.conf /Per Jessen, Zürich
Per Jessen wrote:
Not necessarily. Running an imap server through xinetd is one option, but I think running it as a stand-alone daemon is probably better. I tend to use xinetd for on-demand, but infrequently used services.
What are the pros and cons of using xinetd for such services?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-05-24 at 05:44 -0400, James Knott wrote:
Not necessarily. Running an imap server through xinetd is one option, but I think running it as a stand-alone daemon is probably better. I tend to use xinetd for on-demand, but infrequently used services.
What are the pros and cons of using xinetd for such services?
Conserving memory, for instance: the daemons are not loaded till they are really needed; this means, obviously, that it will respond slower. Depending on the daemon, it might not keep track of previous or even simultaneous sessions, and will have less control. Depends on the daemon in question. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEdECttTMYHG2NR9URAhXtAJ0To0ohJLkvOY8fBRFdpluHcUwMMACgjW/Y K74PZH7wRwCjkTcgP+SCVR0= =Xh5C -----END PGP SIGNATURE-----
James Knott wrote:
Per Jessen wrote:
Not necessarily. Running an imap server through xinetd is one option, but I think running it as a stand-alone daemon is probably better. I tend to use xinetd for on-demand, but infrequently used services.
What are the pros and cons of using xinetd for such services?
I think both are quite subjective - Pro: I don't like running daemons for infrequently used services, they clutter up displays and make the system appear to be more loaded it really is. Con: possibly slightly increased response time on the first call. /Per Jessen, Zürich
The problem was that I didn't have any service active.
Thanks
Juan Pablo
On 5/24/06, Per Jessen
Juan Pablo Romero wrote:
Hello
I'm trying to configure imap; I gather it is necessary to have xinetd running first, is this correct?
Not necessarily. Running an imap server through xinetd is one option, but I think running it as a stand-alone daemon is probably better. I tend to use xinetd for on-demand, but infrequently used services.
OK, the problem is xinetd refuses to start, it displays this message:
# rcxinetd start Starting INET services. (xinetd) failed #
Have you configured the services that you wish xinetd to provide? I suspect it might fail to start if it hasn't got any services to offer. Check /etc/xinet.d/ and /etc/xinetd.conf
/Per Jessen, Zürich
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2006-05-23 at 20:46 -0500, Juan Pablo Romero wrote:
OK, the problem is xinetd refuses to start, it displays this message:
# rcxinetd start Starting INET services. (xinetd) failed #
I don't have any idea where to look for debug info, or otherwise look for a clue.
Look in the log files; start with '/var/log/messages'. The reason will be there. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFEdD+vtTMYHG2NR9URAvW1AJ4hvJRuiF29r3XMysLusrMlzPQMjgCeI/L2 +swOdr67eZur55kxf3Z6Hyc= =ZShN -----END PGP SIGNATURE-----
participants (4)
-
Carlos E. R. -
James Knott -
Juan Pablo Romero -
Per Jessen