files: action ambiguity

[Wil Cooley]

I'm trying to find the right action for a files section.  What I want
is:
  1. Create the file if it does not exist with appropriate perms
  2. Fix permissions if it does exist but perms are wrong
  3. Not update timestamps (and needlessly define classes!)

I'm using 2.1.13; I've tried 'create', 'fixall', 'fixplain' and 'touch'.
'touch' does 1 & 2, but also needlessly defines classes.  'fixall' and
'fixplain' won't create the file if missing.  'create' does 1 & 3, but
not 2 (according to the docs).  If this does not exist, consider it an
RFE.  If it does exist but I cannot find it in the docs, consider it an
RFE for the reference guide.  I could, I suppose, use multiple files
sections with different actions, but it seems like a bug that it is not
able to do this.

Background:

I'm encountering this problem maintaining syslog files on Linux and
Solaris systems.  Solaris's syslogd won't create log files if they do
not exist, so I need to manually create them.  Linux's will create them,
but not with the permissions I want (my logrotate config will fix the
permissions, but I don't want to rely solely on that).  Using 'touch'
defines classes, so if I define a class to reload syslogd, it happens
every time cfagent is run.


Wil
-- 
Wil Cooley                                 wcooley@nakedape.cc
Naked Ape Consulting                        http://nakedape.cc
* * * * Linux, UNIX, Networking and Security Solutions * * * *

signature.asc
Description: This is a digitally signed message part