Xref: utzoo comp.unix.questions:20252 alt.sys.sun:570 Path: utzoo!mnetor!geac!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!math.lsa.umich.edu!emv From: emv@math.lsa.umich.edu (Edward Vielmetti) Newsgroups: comp.unix.questions,alt.sys.sun Subject: Re: crontab update Message-ID: Date: 28 Feb 90 17:15:01 GMT References: <855@edstip.EDS.COM> <24572@princeton.Princeton.EDU> Sender: news@math.lsa.umich.edu Distribution: na Organization: University of Michigan Math Dept., Ann Arbor MI. Lines: 25 In-reply-to: tr@samadams.princeton.edu's message of 28 Feb 90 16:19:23 GMT In article <24572@princeton.Princeton.EDU> tr@samadams.princeton.edu (Tom Reingold) writes: Is SysV-style cron, there is no /usr/lib/crontab. Instead, there are files called /usr/spool/cron/crontabs/name, where name is a login name. There is probably a file called root, which is probably what the guy was talking about if he has SysV-style cron. The crontab(1) command sends the proper signal to the cron process to reread the file. It is then kept in memory. Note that SunOS 4.x has SysV-style cron. 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. crontab doesn't communicate with signals at least in SunOS 4.x. It writes something to /var/spool/cron/FIFO, but what? Here's the trace I got: open ("/var/spool/cron/FIFO", 05, 037777777776) = 3 write (3, "".., 26) = 26 strings on crontab(1) doesn't help, anyone with sources care to decode this? --Ed