Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!chinacat!chip From: chip@chinacat.Unicom.COM (Chip Rosenthal) Newsgroups: comp.unix.xenix Subject: Re: cron FIFO in mounted spool filesystem Message-ID: <1460@chinacat.Unicom.COM> Date: 4 Aug 90 00:40:29 GMT References: <8224@scorn.sco.COM> <8353@scorn.sco.COM> Distribution: na Organization: Unicom Systems Development, Austin, TX Lines: 23 In article gar@spiff.UUCP (Gordon Runkle) writes: >In article <8353@scorn.sco.COM> rogerk@sco.COM (Roger Knopf 5502) writes: > 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? A bit of context. I was reading into the situation that it was the size of /usr/spool/news which was pushing the original poster into creating a /usr/spool filesystem. If that was the case, I suggested that making it just a news filesystem was a good idea for two reasons: first it doesn't break /etc/rc.d/*, and second if your filesystem fills you aren't going to get mail messages and such dropped on the floor. Certainly, starting cron after the mount would work, and arguably that's a much more sensible sequence. But I'm a strong believer of keeping news off in a seperate corner. I'm a subscriber to the "Gaseous Theory of USENET" (news expands to occupy the available volume). -- Chip Rosenthal | You aren't some icon carved out chip@chinacat.Unicom.COM | of soap, sent down here to clean Unicom Systems Development, 512-482-8260 | up my reputation. -John Hiatt