Date: Tue, 29 Mar 2005 22:13:45 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Matteo Riondato <rionda@gufi.org> Cc: freebsd-bugs@freebsd.org Subject: Re: conf/36392: [feature request] cron starts before vi recover, and vi recover isnt dont securely Message-ID: <45221.1112127225@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 29 Mar 2005 22:10:05 %2B0200." <20050329201005.GE916@kaiser.sig11.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20050329201005.GE916@kaiser.sig11.org>, Matteo Riondato writes: > >--qKojvbh47KHQqxue >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Tue, Mar 29, 2005 at 10:03:41PM +0200, Poul-Henning Kamp wrote: >> In message <200503292000.j2TK0Dl6082442@freefall.freebsd.org>, Matteo Rio= >ndato=20 >> writes: >>=20 >> > It's not really clear where is the bug, anyway, according to rcorder >> > -s nostart /etc/rc.d/*, virecover is launched before cron and inetd. >> > I think this PR can be closed. >>=20 >> I don't know if this is really related/relevant, but it bugs me that >> we run virecover on systems where no mail service is configured. > >Do you think that we should not even run virecover on such systems or >that we should not send a mail to the user?=20 It's the mail-sending bit which bugs me, in some configurations this simply hangs boot for how ever long it takes for it to realize that it can't. Possibly the underlying issue is really lack of DNS I'm not sure. Of course it begs the question about what to do about stuff like cron output which is also mailed... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45221.1112127225>