Return to BSD News archive
Xref: sserve comp.unix.questions:33235 comp.unix.programmer:8986 comp.unix.aix:21144 comp.unix.shell:8703 comp.unix.bsd:11825 Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!decwrl!pa.dec.com!vixie From: vixie@pa.dec.com (Paul A Vixie) Newsgroups: comp.unix.questions,comp.unix.programmer,comp.unix.aix,comp.unix.shell,comp.unix.bsd Subject: Re: crontab having effect on several machines Date: 15 Apr 93 23:07:04 Organization: DEC Network Systems Lab Lines: 15 Message-ID: <VIXIE.93Apr15230704@cognition.pa.dec.com> References: <1993Apr13.205021.27788@sifon.cc.mcgill.ca> <C5JD15.12A@crdnns.crd.ge.com> <1qko75INNpsi@early-bird.think.com> NNTP-Posting-Host: cognition.pa.dec.com In-reply-to: barmar@think.com's message of 15 Apr 1993 22:39:33 GMT [barry margolin] > That wouldn't necessarily work. On machines with SysV-style cron, changes > to crontab files won't be noticed automatically; the files are only read > when cron starts up, and you have to use the crontab(1) command to update > them. So if you NFS mounted the crontabs directory and used crontab(1) on > one machine, it wouldn't update cron on the other machines. fortunately, though, there's a free version of cron that doesn't have those problems. just the same, though, bill's answer is the best: even though it would sort-of-work, it's a bad idea to share crontabs with NFS. -- Paul Vixie, DEC Network Systems Lab Palo Alto, California, USA "Don't be a rebel, or a conformist; <vixie@pa.dec.com> decwrl!vixie they're the same thing, anyway. Find <paul@vix.com> vixie!paul your own path, and stay on it." -me