Command Usage: samadmin v8_1_5
samadmin autodest audit directories

Just having some fun...
This command is deprecated (no longer actively maintained).
Use at your own risk.

Command Description:

This command performs an auditing function on the number of files currently
in the MSS (Mass Storage Systems) file system.

The intended mode of running is as a daily cron process that checks for any
new files in a directory since yesterday (default for the --date argument)
and report any directories that have filled beyond a specified threshold 
(--max_files argument).  

If any directories fill beyond this threshold, a new directory should be 
created to handle future files. 

This command can be run from the command line without the email option 
specified.  When run with the debug flag (-d), details of all directories 
monitored with the last access times displayed as well as other information.

The command can operate in either of 2 modes:

 1. database mode (DEFAULT)

    The audit is performed using the SAM DATA_FILES table and counts the number
    of files per directory and the last create_date for each directory.  It
    will only report on directories exceeding the specified threshold 
    (--max_files) and have been created in the last day (--date argument).

    It should be noted that the SQL statement performing the summary may take
    a significant (1 minute or better) to query and summarize the data.  This
    should not be cause for alarm.

    By running in this mode, rather than 'filesystem' mode, we remove any impact
    on the /pnfs file system and any performance issues this audit might have
    on storing files.  The SQL query should not have ANY impact on storing 
    files.  (I only mention this as it had been raised as a concern when
    thie command was first implemented and performed it's audit in 'filesystem'
    mode.)

 2. filesystem mode (--filesystem argument)

    When auditing the physical file system in order to expedite the process, 
    the command first 'stats' the directory to determine if it has been written
    to / modified since a specified date (--date option).  If it has not been 
    modified (assumes no new files), then it continues on to the next directory
    assuming that this directory is no longer actively being written to.  This 
    can sometimes lead to misleading results due to the manual procedure 
    sometimes used to mark a file as bad in the ENSTORE system.
          

Usage:
       samadmin autodest audit directories [--options] [-flags]

Where:


  --options:
	                  --filesystem # 
            If specified, the audit will be performed against
            the physical file system defined in SAM's
            AUTO_DESTINATION table by the destination path /
            location_id.
            When specified, this command must be run from a
            platform that has all the auto destination paths
            mounted. 
            
	    --corbaCallTimeout=<value> # time in seconds for CORBA method calls to return before timing out (default: 0; zero implies no timeout)
	                --date=<value> # 
            Checks only those directories that have been written
            to after this date. 
                             
            FORMAT:  YYYY/MM/DD
                             
            The date MUST be entered in the correct format as
            there is no validation performed and the comparison
            on the 'last modified' date of the directory is a
            string comparision.  Unpredictable results will 
            occur.
                             
            DEFAULT: yesterday at 00:00:00
            
	               --email=<value> # 
            Email address (group) that will receive 
            notice of any abnormalities found.
            DEFAULT: no email sent 
            
	            --maxFiles=<value> # 
            Maximum number of files allowed in any one 
            directory. Any directories containing files 
            beyond this value will be reported. 
            DEFAULT: 10,000 files.
            
	       --retryInterval=<value> # retry interval base in seconds; will multiply this base times retryCount (default: 5)
	         --retryJitter=<value> # retry jitter, random jitter added to base retry interval times retryCount (default: 5)
	       --retryMaxCount=<value> # number of times to retry CORBA calls for retriable exceptions (default: 25; zero implies no retries)

   -flags:
	                            -c # automatically close all servants after each method call
	                            -d # debug mode
	                            -s # retrySilently mode (do not issue messages to stderr on proxy retries)
	                            -t # time-it mode (print additional info on timings)
	                            -v # verbose mode

Required Data Types:
	              corbaCallTimeout : int 
	                          date : SamTime 
	                         email : string 
	                      maxFiles : long 
	                 retryInterval : int 
	                   retryJitter : int 
	                 retryMaxCount : int 

You may omit "-c" if the $SAM_PYAPI_AUTO_CLOSE_SERVANTS environmental variable is set.
You may omit "--corbaCallTimeout=<value>" if the $SAM_PYAPI_CORBA_CALL_TIMEOUT environmental variable is set.
You may omit "--retryInterval=<value>" if the $SAM_PYAPI_RETRY_INTERVAL environmental variable is set.
You may omit "--retryJitter=<value>" if the $SAM_PYAPI_RETRY_JITTER environmental variable is set.
You may omit "--retryMaxCount=<value>" if the $SAM_PYAPI_RETRY_MAX_COUNT environmental variable is set.
You may omit "-s" if the $SAM_PYAPI_RETRY_SILENTLY environmental variable is set.

UNIX ExitStatus:
	             Success :   0
	Unhandled exceptions : 127


See Also: