Date: Wed, 28 Mar 2001 12:56:42 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Alfred Perlstein <bright@wintelcom.net> Cc: Brian Somers <brian@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/etc rc Message-ID: <92684.985777002@critter> In-Reply-To: Your message of "Wed, 28 Mar 2001 02:52:35 -0800." <20010328025234.T9431@fw.wintelcom.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20010328025234.T9431@fw.wintelcom.net>, Alfred Perlstein writes: >* Poul-Henning Kamp <phk@critter.freebsd.dk> [010328 02:25] wrote: >> In message <20010328022334.S9431@fw.wintelcom.net>, Alfred Perlstein writes: >> >* Brian Somers <brian@FreeBSD.org> [010328 02:13] wrote: >> >> brian 2001/03/28 02:13:27 PST >> >> >> >> Modified files: >> >> etc rc >> >> Log: >> >> Remove sockets found in /var/run or /var/spool/lock at boot time >> >> (as well as files). >> > >> >This may be a bad idea. >> > >> >Some applications may use these files as an indication of an >> >unorderly shutdown (kill -9 / crash). And refuse to start unless >> >repair utilities are run (or run them automatically). >> > >> >What do you think? >> >> I think such applications are badly designed since the file >> could disappear for exactly the same reasons which force the >> application to run recovery... > >You mean after fsync() returns? I mean after a filesystem is trashed due to a disk-crash and restored from a backup... -- 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?92684.985777002>