MAN page from Old RedHat 5.X safedelete-1.3-4.i386.rpm

safedelrc

Section: File Formats (5)
Index

NAME

safedelrc - safedelete options file

DESCRIPTION

The.Safedelrcfileis used to specify, at the filename level, how longto retain files which have been removed by the safedelete command.It contains three sections which contain the informationrequired for safedelete, undelete, and safedelchk to work correctly.

IMPORTANT
The .Safedelrcfile is optional, but must reside in your $HOME directoryif you decide to use it.If you have a .Safedelrc file in your $HOME directory, all threesectionsMUSTbe present. You'll get unpredictable results if one of the sectionsis missing.

Each section begins with a header label and ends with a trailer label.These labels must separate each of the sections or you'll get unpredictableresults. All statements in the .Safedelrc must begin in column 1.

SECTIONS

[safedays]

This section specifies a filename pattern and the number of days the safedeleted file should be kept on the system. Each line containsone or more patterns, separated by commas, along with thenumber of days. One or more spaces separates the patterns and the number.The only wildcard character accepted is the asterisk ("*")and at most 1 may appear in the filename pattern. The asterisk can appearanywhere in the pattern (beginning, end, or middle).

If the number of days iszerothen the file(s) on that line will not be safedeleted. Also, the numberof days specified cannot be larger than the maximum number of days setwhen SafeDelete was installed. If a number is larger than the maximum,the maximum number of days will be used in its place.

If a directory is specified in the pattern the number of days specifiedapplies to the files in that directory and all of its subdirectories.

Syntax: pattern1[,pattern2][,patternx]n

Example:

[safedays]
core 0
*.o,/tmp/* 1
/usr/src/*.c 10
[endsection]

In the above example no core files will be safedeleted. All files endingwith .o and all files in the /tmp directory,and all of its subdirectories, will be safedeleted for only1 day. Finally, all files ending with .c in the /usr/src directory,and all of its subdirectories, willbe safedeleted for 10 days.

[compression]

This section specifies which compression utility to use when compressingfiles. Each line specifies one or more filename patterns, separated bycommas, followed by a pair of commands separated by a forward slash ("/").The first command in the pair is the compression command while the secondcommand is the decompression command.

You can specify up to 40 characters for each command.

If some files are not to be compressed, you can specifynonein place of the command pair.

The filename pattern can contain the wildcard character "*", but at most 1 is permitted in each pattern.

Syntax:

pattern1[,pattern2][,patternx ]
{ <compress cmd>/<decompress cmd> | none }

Example:

[compress]
*.c gzip -9/gunzip
/usr/local/*.tex compress/uncompress
*.gz,*.Z,*.tgz none
[endsection]

In this example, all files ending with .c will be compressed using thecommand gzip -9 and will be decompressed with the gunzip command. Allfiles ending with .tex in the /usr/local directory, and all of itssubdirectories, will use the compressand uncompress commands while any file ending with .gz, .Z or .tgz will not be compressed at all.

[suffix]

This section describes the filename suffix added by each compressionutility. The suffix section is critical because the safedeletecommand uses it to correctly determine the filename of the compressed file.The format of each line is the name of a compression utility commandfollowed by at least one space and the acutal suffix.

You can specify up to 8 characters for each suffix (a dot followed by upto 7 characters).

Syntax:

command1[,command2][,commandx].suffix

Example:

[suffix]
gzip .gz
compress .Z
[endsection]

In this example the gzip command requires the .gz suffixwhile the compress command uses the .Z suffix.

[options]

This section specifies a variety of options which are used byall of the safedelete commands.

Syntax:

lockbusy <action>- this option determines what will happen if the lock onthe .safedelete.log is in use.

Values for <action>:

wait- the command will wait until the lock becomes available.A message is issued every 5 seconds if thelock is still unavailable.
prompt- the command will issue a prompt every 5 seconds asking if the user still wishes to wait. This is the default behavior.

quit- if the lock is unavailable execution is terminated.

Example:

[options]
lockbusy quit
[endsection]

In this example if the lock is unavailable the command isterminated.

This document was created byman2html,using the manual pages.