Re: cfexecd and chmod($input_dir)

[Chip Seraphine]

I have the same problem.  I wanted mine to be 1770 in order to allow sysadmins 
to set flag files as themselves instead of root (so we could better account 
for who did what), but all it did was fight with the hard coded chmod...

On Saturday 05 June 2004 03:12, Mark.Burgess@iu.hio.no wrote:
> 
> The directory must be trusted. Why do you care?
> 
> M
> 
> On  4 Jun, Will Lowe wrote:
> > I'm running v 2.1.0p1.
> > 
> > Why does cfexecd insist on doing chmod($input_dir) whenever it runs?
> > There's nothing secret in my cfagent configs, so I had update.conf set
> > to set the input dir to 0755.
> > 
> > Looks like the code is at line 218 in cfexecd.c:
> > 
> > snprintf(VBUFF,bufsize,"%s/inputs",WORKDIR);
> > chmod(VBUFF,0700); 
> > snprintf(VBUFF,bufsize,"%s/outputs",WORKDIR);
> > chmod(VBUFF,0700);
> > 
> 
> 
> 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Work: +47 22453272            Email:  Mark.Burgess@iu.hio.no
> Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 
> 
> 
> _______________________________________________
> Help-cfengine mailing list
> Help-cfengine@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-cfengine
> 

-- 

Chip Seraphine
Unix Administrator
TradeLink, LLC
312-264-2048
chip@trdlnk.com