Xref: utzoo comp.unix.questions:20292 alt.sys.sun:580 Path: utzoo!mnetor!geac!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucsd!ames!dftsrv!mimsy!mojo!smaug From: smaug@eng.umd.edu (Kurt Lidl) Newsgroups: comp.unix.questions,alt.sys.sun Subject: Re: crontab update Message-ID: <1990Mar1.195750.25818@eng.umd.edu> Date: 1 Mar 90 19:57:50 GMT References: <855@edstip.EDS.COM> <24572@princeton.Princeton.EDU> Sender: news@eng.umd.edu (The News System) Distribution: na Organization: Dragon Finishing School of Unix and Magic Lines: 20 In article emv@math.lsa.umich.edu (Edward Vielmetti) writes: >In article <24572@princeton.Princeton.EDU> tr@samadams.princeton.edu (Tom Reingold) writes: >>[crontab description for SunOS 4.0, SysV deleted] > >This is OK but -- I have a bunch of diskless machines with their >crontab files all mounted via NFS from a server. To update the whole >batch I need to log in to every machine and run 'crontab' -- if >I could automate the procedure somewhat I'd like to. Well, you can do some funky things like this: cp proto_cron /export/root/client/var/spool/cron/crontabs/root rsh client crontab -l This will cause cron to re-read the file off of disk. I would rather that cron periodically use stat() the crontab file and re-read it if it needed to... -- /* Kurt J. Lidl (smaug@eng.umd.edu) | Unix is the answer, but only if you */ /* UUCP: uunet!eng.umd.edu!smaug | phrase the question very carefully. */