Provided by: fcron_3.0.1-1.2_i386
fcron.conf - configuration file for fcron and fcrontab
This page describes the syntax used for the configuration file of
fcrontab(1), fcrondyn(1) and fcron(8).
Blank lines, line beginning by a hash sign (#) (which are considered
comments), leading blanks and tabs are ignored. Each line in a
fcron.conf file is of the form
name = value
where the blanks around equal-sign (=) are ignored and optional.
Trailing blanks are also ignored.
The following names are recognized (default value in parentheses):
"VALID VARIABLES IN A FCRON.CONF FILE"
Fcron spool directory.
Location of fcron pid file (needed by fcrontab to work
Location of fcron fifo file (needed by fcrondyn to communicate
Location of fcron.allow file.
Location of fcron.deny file.
Location of default shell called by fcron when running a job.
Location of mailer program called by fcron to send job output.
Location of default editor used when invoking "fcrontab -e".
File-paths and directories are complete and absolute (i.e.
beginning by a "/").
To run several instances of fcron simultaneously on the same system,
you must use a different configuration file for each instance. Each
instance must have a different fcrontabs, pidfile and fifofile. Then,
use fcron(8)’s command line option -c to select which config file (so
which instance) you refer to.
Configuration file for fcron, fcrontab and fcrondyn: contains
paths (spool dir, pid file) and default programs to use (editor,
shell, etc). See fcron.conf(5) for more details.
Users allowed to use fcrontab and fcrondyn (one name per line,
special name "all" acts for everyone)
Users who are not allowed to use fcrontab and fcrondyn (same
format as allow file)
/etc/pam.d/fcron (or /etc/pam.conf)
PAM configuration file for fcron. Take a look at pam(8) for more
If you’re learning how to use fcron from scratch, I suggest that you
read the HTML version of the documentation (if your are not reading it
right now! :) ): the content is the same, but it is easier to navigate
thanks to the hyperlinks.
Thibault Godouet <firstname.lastname@example.org>