- Use of application tags for a daemon
- Use of filename tags instead of command ones for a file
This commit is contained in:
parent
7faeda5c56
commit
9e316c8ae9
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=22698
1 changed files with 2 additions and 2 deletions
|
|
@ -486,14 +486,14 @@ run_rc_command "$1"</programlisting>
|
|||
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
|
||||
with <application>inetd</application> and its configuration is
|
||||
described in depth in the
|
||||
<link linkend="network-inetd">inetd</link> section.</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
|
||||
these processes as the <filename>crontab</filename>'s file
|
||||
owner. This allows regular users to start and maintain some
|
||||
applications.</para>
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue