samples del [-<user>] <file> ...
samples is the single-instance version of sample, if you have not read the sample manual yet you should read it first, as it contains the basic syntax used.
the samples program creates and deletes files in ~/.sample_spool/, which contain the exact same syntax/functionality as a ~/.sample file. the only two differences between a ~/.sample file and a file in ~/.sample_spool/ is that after a command is triggered or a time-to-live limit is hit, the file in ~/.sample_spool/ will be deleted, making it a single-instance.
samples is designed to monitor a single file per sample file. however, this is not required. custom files may be dropped in ~/.sample_spool/ and treated the same as a ~/.sample file, except it is deleted afterwords.
if no file is matched (ie. it was deleted/moved) during a sampled processor run of ~/.sample_spool/, it will delete the corresponding single-instance sample file automatically.
"if type has past time for file then run exec"
OR, for filesize comparisons (where type is S or s):
"if type is larger/smaller than size for file then run exec"
if ttl is specified; the single-instance sample file will be deleted after the specified period of time. the ttl time format is the same as for monitoring times (ie. "1Y6M" is 1.5 years)
if shell is specified; "SHELL=shell" will be placed in the single-instance sample file (this may or may not be allowed depending on your sample.conf configuration)
# samples add ~/README.TXT A 1w "mv -- %s ~/old" 1M
this example would monitor ~/README.TXT to see if it has been read/accessed (A) in the last week, if not it will execute "mv -- %s ~/old" and delete the corresponding sample file in ~/.sample_spool/, so not to execute it again. if the file is consistently read for 1 month the sample file will be deleted even though the command was never executed, as it hit the time-to-live (ttl)
# samples del ~/README.TXT
this example would delete any corresponding sample file(s) that are montioring ~/README.TXT