> I was just wondering how to get rid of these errors in my startup:
>
> Jan 26 22:12:19 culverk inetd[739]: ftp/tcp: ipsec initialization
> failed; out entrust
> Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization
> failed; in entrust
> Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization
> failed; out entrust
> Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization
> failed; in entrust
> Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization
> failed; out entrust
> Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization
> failed; in entrust
> Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization
> failed; out entrust
>
> Maybe there was a message on here that I overlooked, I'm not sure, but how
> exactly do I get rid of them?
Now IPsec related control functionalities are added to inetd,
and when kernel is not compiled with IPSEC related options,
IPsec related socket initialization fails and those messages
are print out.
It is not harmful but I should have lower the syslog level,
sorry.
I'll soon fix it.
Thanks,
Yoshinobu Inoue
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
