Return to BSD News archive
Xref: sserve comp.unix.questions:33220 comp.unix.programmer:8980 comp.unix.aix:21138 comp.unix.shell:8696 comp.unix.bsd:11822
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!think.com!barmar
From: barmar@think.com (Barry Margolin)
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 1993 22:39:33 GMT
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 16
Message-ID: <1qko75INNpsi@early-bird.think.com>
References: <1993Apr13.205021.27788@sifon.cc.mcgill.ca> <C5JD15.12A@crdnns.crd.ge.com>
NNTP-Posting-Host: telecaster.think.com
In article <C5JD15.12A@crdnns.crd.ge.com> davidsen@crd.ge.com (bill davidsen) writes:
> If you have the guts and NFS you could export the crontabs directory
>to all machines in the netgroup and mount it. It sounds good, but would
>affect all the machines and all the users, not just root.
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.
--
Barry Margolin
System Manager, Thinking Machines Corp.
barmar@think.com {uunet,harvard}!think!barmar