os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Finish my work in the starting services section.

Browse source
This commit is contained in:
Tom Rhodes 2004-09-21 02:54:23 +00:00
parent c2ee4de7dc
commit 77b21c576f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=22408
1 changed files with 24 additions and 15 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

39
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -479,24 +479,33 @@ run_rc_command "$1"</programlisting>
<filename role="directory">/etc/rc.d</filename> directory.
Yet, that has the potential to upset the &man.mergemaster.8;
utility when used in conjunction with software upgrades.</para>
</sect2>
<para>Some services expect to be invoked by &man.inetd.8; when a
connection is received on a suitable port. This is common for
mail reader servers (POP and IMAP, etc.). These services are
enabled by editing the file <filename>/etc/inetd.conf</filename>.
See &man.inetd.8; for details on editing this file.</para>
<sect2>
<title>Using Services to Start Services</title>
<para>It is also possible to use the &man.cron.8; daemon to start
system services. This approach has a number of advantages, not
least being that because &man.cron.8; runs these processes as the
owner of the <command>crontab</command>, services may be started
and maintained by non-<username>root</username> users.</para>
<para>Other services, such as <acronym>POP</acronym>3 server
daemons, <acronym>IMAP</acronym>, etc. could be started using
the &man.inetd.8;. This involves installing the service
utility from the ports collection with a configuration line
appended to the <filename>/etc/inetd.conf</filename> file,
or uncommenting one of the current configuration lines. Working
with <command>inetd</command> and its configuration is
described in depth in the
<link linkend="network-inetd">inetd</link> section.</para>
<para>This takes advantage of a feature of &man.cron.8;: the
time specification may be replaced by <literal>@reboot</literal>,
which will
cause the job to be run when &man.cron.8; is started shortly after
system boot.</para>
<para>In some cases, it may be more plausible to use the
&man.cron.8; daemon to start system services. This approach
has a number of advantages because <command>cron</command> runs
these processes as the <command>crontab</command>'s file
owner. This allows regular users to start and maintain some
applications.</para>
<para>The <command>cron</command> utility provides a unique
feature, <literal>@reboot</literal>, which may be used in place
of the time specification. This will cause the job to be run
when &man.cron.8; is started, normally during system
initialization.</para>
</sect2>
</sect1>