." intlink tagname rest
.de intlink
. ie \\n[www-html] \{\
.  HTML <a href="#\\$1">\\$1</a>\\$2
. \} 
. el \{ \fB\\$1\fR\\$2 \} 
..
." extlink URL text rest
.de extlink
. ie \\n[www-html] \{\
.  HTML <a href="\\$1">\\$2</a>\\$3
. \} 
. el \{ \fB\\$1\fR\\$3 \} 
..
.de manlink
. ie \\n[www-html] \{\
.  HTML <a href="\\$1">\\$2</a>\\$3
. \} 
. el \{ \fB\\$2\fR\\$3 \} 
..
.de paragraph
.HTML <p>
.P
..
.de section
. ie \\n[www-html] \{\
.HTML <p><h2>\\$1</h2><p>
. \}
. el \{
.SH \\$1
. \}
..
.de subsection
. ie \\n[www-html] \{\
.HTML <p><h3>\\$1</h3><p>
. \}
. el \{
.SS \\$1
. \}
..
." type name (args ..."
.de func
.HTML <dl>
.HTML <dt>
\\$1 \fB\\$2\fR\\$3
..
.de args
.br
.HTML <dd>
    \\$1
..
.de endfunc
.br
.HTML </dl>
.P
..
.de options
. HTML <dl>
..
.de option
. ie \\n[www-html] \{\
. HTML "<dt>\\$1<dd>"
. \}
. el \{
.HP
\\$1
.br
. \}
..
.de optionparagraph
.HTML <p>
.IP
..
.de endoptions
. HTML </dl>
..
.de list
.HTML <ul>
..
.de entry
. ie \\n[www-html] \{\
. HTML "<li>\\$1"
. \}
. el \{ .TP 3
*
\\$1
\}
..
.de endlist
.HTML </ul>
..
.ds PA uschedule
.ds VE 0.7.1
.ds CL admin
.TH uscheduleconf 1 \*(VE \*(PA      
.hy 0
.URL "Uwe Ohse" ../uwe.html
.br
.URL "The uschedule package" ../uschedule.html
.paragraph
.SH NAME
uscheduleconf - configure a scheduling service
.LINE
.SH SYNOPSIS
\fBuscheduleconf\fR DIR ACCT LOGACCT [JOBDIR [LOGDIR]]
.SH DESCRIPTION
\fBuscheduleconf\fR creates a svscan service directory \fIDIR\fR, which
starts a service to uschedule for the user \fIACCT\fR. The jobs will be read
from \fIJOBDIR\fR (or ~\fIACCT\fR/.uschedule, if \fIJOBDIR\fR is not given
or only contains a minus character).
.paragraph
Logging information will be written to \fILOGDIR\fR 
(or ~\fIACCT\fR/.uschedule/log, if \fILOGDIR\fR is not given), using the
the account \fILOGACCT\fR.
.paragraph
Version before 0.7.0 allowed to give "-" for ACCT to use the current user
and "-" for LOGACCT to use ACCT for LOGACCT, but the code turned out to
be buggy. See the NEWS file of the uschedule package for more information.
.SH "OPTIONS"
.options
.option "-n, --no-user-change"
Do not change file ownership and do not switch user ids.
.optionparagraph
The default is to make ACCT and LOGACCT the owners of JOBDIR, LOGDIR and
the file therein, and to switch to ACCT and LOGACCT before running 
uscheduled and the logging program.
.optionparagraph
With this option the caller will be the owner of all files created and 
the programs will run with all the rights they inherit.
.optionparagraph
This option was added in version 0.7.0.
.endoptions
.SH "ENVIRONMENT"
In \fIJOBDIR\fR/env a number of environment variables are set (one file
per variable). HOME, SHELL, USER and LOGNAME are set to values taken 
from the system password database.
.br
The PATH variable is set to /command:/usr/local/bin:/usr/bin/:/bin 
for any user not having an uid of 0. For users with uid 0 
/usr/local/sbin:/usr/sbin:/sbin will be appended. 
.paragraph
All these variables may be changed.
.paragraph
.SH "SECURITY"
Keep the following rules in mind:
.list
.entry
Do not ever create a service directory \fIDIR\fR in an insecure place.
Nobody but you - the system administrator - must be able to write to it.
Especially do not ever create this directory in the users $HOME. You
would be giving away instant root access!
.entry
Do not ever create \fIJOBDIR\fR and \fILOGDIR\fR in an insecure place.
These directories and the content must only be writable by the user
for which the service is run.
.entry
Be careful about \fILOGACCT\fR. If you set up a scheduling service for
a user then \fILOGACCT\fR should be this user. If you are setting up
a scheduling service for a system account then you may want to use
a different user for logging purposes (while this is local policy i can't
think of any reason why the logging should run as root).
.entry
Resource limits may be configured in \fIDIR/run\fR and \fIDIR/log/run\fR.
The defaults are most possibly not right for every system. Keep in mind
that perl eats lots of resources and that a multilog processor may use
perl ...
.endlist
.SH "EXAMPLES"
.subsection "Setup a scheduler for system services"
Create a uschedule service for root, with the service
directory /etc/root-schedule and the logging done to 
/var/log/root-schedule under the "misclog" account.
.paragraph
.nf
.HTML <pre>
    uscheduleconf /etc/root-schedule root misclog \\
             /etc/root-schedule/jobs /var/log/root-schedule
.HTML </pre>
.fi
.subsection "Setup a scheduler for a user"
Create a schedule service for uwe, having the trusted 
commands in /etc/uwe-schedule and any parts uwe can
change in ~uwe/.uschedule:
.paragraph
.nf
.HTML <pre>
    uscheduleconf /etc/uwe-schedule uwe uwe \\
             ~uwe/.uschedule ~uwe/.uschedule/logs
.HTML </pre>
.fi
.SH AUTHOR
Uwe Ohse, uwe@ohse.de
.SH "SEE ALSO"
.manlink uschedule.html uschedule(1) ,
.manlink uschedulecmd.html uschedulecmd(1) ,
.manlink intro.html uschedule_intro(7) .
.HTML <!--
.paragraph
The homepage may be more up-to-date, see
.br
http://www.ohse.de/uwe/uschedule.html.
.HTML -->