filetraq(8) [debian man page]

FILETRAQ(8)						      System Manager's Manual						       FILETRAQ(8)

NAME

       filetraq - keep track of changes in config files.

SYNOPSIS

       filetraq --help
       filetraq [filelist] [backupdir]

DESCRIPTION

       This  manual  page  documents briefly the filetraq command.  This manual page was written for the Debian GNU/Linux distribution because the
       original program does not have a manual page.

       FileTraq is a shell script that reads a list of files to watch, runs diff against each file and its backup, and reports any  discrepancies,
       along with keeping a dated backup of the original.

       It's designed to be run as a cron job.

OPTIONS

       This command has two possible invocations, one with one option:

       --help Show summary of options and the default values of the config file and the backup directory.

       and other with no options, a config file or a config file and the backupdir.

       The  debian  version has been modified to read the /etc/default/filetraq configuration file, that lets the administrator change the default
       values of the config file ( file ), the backup directory ( backupdir ), the diff options used to print the filetraq  output  (  diffopts  ,
       e.g.  -p -C 1 or -u ) and the diff order ( difforder , either newold (FileTraq default) or oldnew (traditional Unix default)).

SECURITY

       FileTraq  is  not  well	tested	or hardened.  It runs as root, but all of its config files should only be accessible by root.  No security
       holes are known at this time, but please be careful.

BUGS

       Right now, it doesn't take care of its backups very well.  The dated backups will accumulate in the  backups  directory,  bounded  only	by
       diskspace.

       It only handles text files, it isn't a Tripwire replacement for use with system binaries.

FILES

       /etc/filetraq.conf
       /etc/default/filetraq
       /var/lib/filetraq

SEE ALSO

       diff(1), cron(8).

AUTHOR

       Jeremy Weatherford <xidus@xidus.net>
       Homepage: http://filetraq.xidus.net/

       This manual page was written by Sergio Talens-Oliag <sto@debian.org>, for the Debian GNU/Linux system (but may be used by others).

								     June 2001							       FILETRAQ(8)

BACKUP.D(5)							backupninja package						       BACKUP.D(5)

NAME

       BACKUP.D - Action configuration files for backupninja(1).

SYNOPSIS

       /etc/backup.d/*

DESCRIPTION

       To preform the actual backup actions, backupninja processes each action configuration file in /etc/backup.d according to the file's suffix.

       .sh	 run this file as a shell script.

       .rdiff	 backup action for rdiff-backup.

       .dup	 backup action for duplicity.

       .maildir  backup action for slow, incremental rsyncs of tens of thousands of maildirs.

       .mysql	 backup action for safe MySQL dumps.

       .pgsql	 backup action for safe PostgreSQL dumps.

       .sys	 backup action for general system reports and hardware information.

       .svn	 backup action for safe backups of subversion repositories.

       .trac	 backup action for safe backups of trac repositories.

       .makecd	 backup action for burning backups to CD/DVD or creating ISOs.

       These files must be owned by root and must not be world or group readable/writable. Support for additional configuration types can be added
       by dropping bash scripts with the name of the suffix into /usr/share/backupninja.

       The configuration files are processed in alphabetical order. However, it is suggested that you name the config files in "sysvinit style."

       For example:
		  10-local.pgsql.disabled
		  15-runthisfirst.sh
		  20-runthisnext.mysql
		  90-runthislast.rdiff

       Typically, you will put a '.rdiff' config file last, so that any database dumps you make are included in the filesystem backup. Action con-
       figurations which end with .disabled are skipped.

       Example	templates for the action configuration files can be found in /usr/share/doc/backupninja/examples. You can also use ninjahelper(1),
       a console based "wizard" for creating backup actions.

SCHEDULING

       By default, each configuration file is processed everyday at 01:00 (1 AM). This can be changed by specifying the 'when' option in a  backup
       action's  config file or in the global configuration file. Special value 'manual' will disable scheduling for the backup action. It is pos-
       sible to run the backup action manually by invoking ninjahelper(1) with --run command line argument.

       For example:
	 when = sundays at 02:00
	 when = 30th at 22
	 when = 30 at 22:00
	 when = everyday at 01
	 when = Tuesday at 05:00
	 when = hourly
	 when = manual

       These values for "when" are invalid:
	 when = tuesday at 2am
	 when = tuesday at 2
	 when = tues at 02

       A configuration file will be processed at the time(s) specified by the "when" option. If multiple "when" options are present, then they all
       apply.  If  two configurations files are scheduled to run in the same hour, then we fall back on the alphabetical ordering specified above.
       The "when" must occur before any sections in the action configuration file.

FILE FORMAT

       The file format of the action configuration files is "ini style." Sections are created by using square bracket. Long  lines  are  connected
       with a backslash. For example:

	  # this is a comment
	  [fishes]
	  fish = red
	  fish = blue
	  [fruit]
	  apple = yes
	  pear = no thanks 
	  i will not have a pear.

SEE ALSO

       backupninja(1), ninjahelper(1), backupninja.conf(5),

AUTHOR

       BACKUPNINJA was written by the riseup.net collective.

riseup								 October 10, 2005						       BACKUP.D(5)