tidy broken

[Wheeler, John]

Just downloaded 2.0.6 from the site (It had the most recent time stamp).
I'm running on Solaris 2.8. The following script works:
[root@cessna sbin]# more /var/cfengine/inputs/enablemonitoring.conf
control:


        actionsequence  = (
                        tidy.enablemonitoring
                        )
tidy:
        enablemonitoring::
                /monitoring
                        pattern=stop
                        age=0
                        inform=true

before I run it:
ls -l /monitoring/                                          
total 0
-rw-r--r--   1 root     other          0 Apr  8 14:15 stop

invoking as follows:
[root@cessna sbin]# ./cfagent --inform --no-splay -f
/var/cfengine/inputs/enablemonitoring.conf
cfengine:cessna: Deleting /monitoring/stop
[root@cessna sbin]# ls -l /monitoring/
total 0

Everything is cool so far. Now when I include the above script in my
cfagent.conf, it never gets to run. The interesting stuff from -d2 is as
follows:

*********************************************************************
 Main Tree Sched: tidy.install pass 1 @ Tue Apr  8 14:15:59 2003
*********************************************************************

Appending [install]

ExpandWildCardsAndDo(/var/cfengine/outputs=/var/cfengine/outputs)
ExpandWildCardsAndDo(/cfengine/outputs=/cfengine/outputs)
ExpandWildCardsAndDo(/outputs=/outputs)
ExpandWildCardsAndDo(=)
TidyWrapper(/var/cfengine/outputs)
enablemonitoring is excluded!
ExpandWildCardsAndDo(/monitoring=/monitoring)
ExpandWildCardsAndDo(=)
TidyWrapper(/monitoring)
GetLock(tidy.install,_monitoring,time=1049829357), ExpireAfter=120,
IfElapsed=1
GetLastLock()
PutLock(last.cfagent_conf.100.cessna.tidy.install._monitoring)
Unable to delete lock
[last.cfagent_conf.100.cessna.tidy.install._monitoring]: D
B_NOTFOUND: No matching key/data pair found
CheckOldLock(lock.cfagent_conf.cessna.tidy.install._monitoring)
Unable to find lock data
lock.cfagent_conf.cessna.tidy.install._monitoring
SetLock(lock.cfagent_conf.cessna.tidy.install._monitoring)
PutLock(lock.cfagent_conf.cessna.tidy.install._monitoring)
Unable to delete lock
[lock.cfagent_conf.cessna.tidy.install._monitoring]: DB_NO
TFOUND: No matching key/data pair found
RecursiveTidySpecialArea(/monitoring)
Changed directory to /monitoring
Checking the inode and device to make sure we are where we think we
are...
IgnoredOrExcluded(/monitoring)
IgnoreFile()
Tidy: opening dir /monitoring
Filename /monitoring/. is classified as ignorable
Filename /monitoring/.. is classified as ignorable
IgnoreFile(stop)
TidyParticularFile(/monitoring/stop,stop)
enablemonitoring is excluded!
Checking tidy topmost directory /monitoring
TidyParticularFile(/monitoring,monitoring)
ReleaseCurrentLock(lock.cfagent_conf.cessna.tidy.install._monitoring)
PutLock(last.cfagent_conf.100.cessna.tidy.install._monitoring)
LockLog(Lock removed normally )
End PATHTIDY:
No home patterns to search
Job start time set to Tue Apr  8 14:15:59 2003

*********************************************************************
 Main Tree Sched: tidy.enablemonitoring pass 1 @ Tue Apr  8 14:15:59
2003
*********************************************************************

                  New temporary class additions
                  --------( Pass 1 )-------
                             enablemonitoring
Actionsequence item tidy
---------------------------------------------------------------------
Tidying Spool Directories
---------------------------------------------------------------------

---------------------------------------------------------------------
Tidying by directory
---------------------------------------------------------------------

ExpandWildCardsAndDo(/var/cfengine/outputs=/var/cfengine/outputs)
ExpandWildCardsAndDo(/cfengine/outputs=/cfengine/outputs)
ExpandWildCardsAndDo(/outputs=/outputs)
ExpandWildCardsAndDo(=)
TidyWrapper(/var/cfengine/outputs)
ExpandWildCardsAndDo(/monitoring=/monitoring)
ExpandWildCardsAndDo(=)
TidyWrapper(/monitoring)
End PATHTIDY:
No home patterns to search
Job start time set to Tue Apr  8 14:15:59 2003


*********************************************************************
 Main Tree Sched: editfiles.nsswitch pass 1 @ Tue Apr  8 14:15:59 2003
*********************************************************************


It does nothing to the "stop" file. It appears to examine the stop file
from a tidy directive from another include. I have three tidy directive
at this point of the execution. One for each of the following
update.conf, installsoftware.conf and enablemonitoring.conf. 

I asked this question before but didn't get a response. Do I need to
protect the first tidy in the update.conf? Why is the tidy from the
installsoftware.conf file examining the /monitoring directory?

Any help would be appreciated.



John Wheeler
jwheeler@us.britannica.com
312-347-7379