Date: Thu, 27 Jan 2000 13:05:59 +0900 From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp> To: culverk@wam.umd.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: ipsec errors Message-ID: <20000127130559K.shin@nd.net.fujitsu.co.jp> In-Reply-To: <Pine.GSO.4.21.0001262233050.14367-100000@rac1.wam.umd.edu> References: <Pine.GSO.4.21.0001262233050.14367-100000@rac1.wam.umd.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000127130559K.shin>