Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!ux1.cso.uiuc.edu!midway!mimsy!prometheus!media!ka3ovk!jando!spiff!spiff!gar From: gar@spiff.UUCP (Gordon Runkle) Newsgroups: comp.unix.xenix Subject: Re: cron FIFO in mounted spool filesystem Message-ID: Date: 27 Jul 90 22:16:33 GMT References: <732@wshb.csms.com> <8224@scorn.sco.COM> <8353@scorn.sco.COM> Sender: gar@spiff.uucp (Gordon Runkle) Distribution: na Organization: Runkle Research: Arlington, VA Lines: 18 In-Reply-To: rogerk@sco.COM's message of 25 Jul 90 02:22:55 GMT In article <8353@scorn.sco.COM> rogerk@sco.COM (Roger Knopf 5502) writes: Chip Rosenthal wisely pointed out that since cron starts before the file systems are mounted, my above solution won't work. He suggests either to hack /etc/rc.d to reverse the order (and neither he nor I recommend doing this) or pick some lower directory than /usr/spool (/usr/spool/news) and make _that_ the mounted file system. Why is putting the cron startup after the filesystems mount bad? I've had mine this way for over a year, and haven't had any difficulty at all with it. Inquiring minds and all that rot... -=gordon=- -- Gordon A. Runkle, Runkle Research UUCP: uunet!men2a!spiff!gar INTERNET: men2a!spiff!gar@uunet.uu.net, gar%spiff%men2a@uunet.uu.net PH: 703-522-0825 OR 202-566-4382