Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!decvax!tektronix!orca!hammer!andrew
From: andrew@hammer.TEK.COM (Andrew Klossner)
Newsgroups: comp.unix.questions
Subject: Re: How to make sendmail re-read the configuration file (and cron)
Message-ID: <2755@hammer.TEK.COM>
Date: Tue, 20-Jan-87 17:07:44 EST
Article-I.D.: hammer.2755
Posted: Tue Jan 20 17:07:44 1987
Date-Received: Wed, 21-Jan-87 22:09:47 EST
References: <136@quacky.mips.UUCP> <201@devon.UUCP> <2409@mcc-pp.UUCP>
Distribution: na
Organization: Tektronix, Inc., Wilsonville, OR
Lines: 18

[]

	"I've got a bunch of diskless suns and rather than have a
	different crontab for all the suns on a server, I have all
	clients crontabs point to the real crontab file.  However, when
	I make a change, it doesn't seem to take unless I kill the cron
	daemon.  I never even thought of stat()!  Of course, it's
	stat()ing the symbolic link (which hasn't changed!) and not the
	real file.  Now, the question I have is why would you ever NOT
	want stat() to resolve the link and stat the actual disk file
	rather than the link???"

Something's wrong.  The 4.2BSD definition of stat(2) says that it gives
the status of the file to which the symlink points.  The lstat(2) call
gives the status of the symlink itself.

  -=- Andrew Klossner   (decvax!tektronix!tekecs!andrew)       [UUCP]
                        (tekecs!andrew.tektronix@csnet-relay)  [ARPA]