diff options
Diffstat (limited to 'documentation/content/en/articles/rc-scripting/_index.po')
| -rw-r--r-- | documentation/content/en/articles/rc-scripting/_index.po | 194 |
1 files changed, 97 insertions, 97 deletions
diff --git a/documentation/content/en/articles/rc-scripting/_index.po b/documentation/content/en/articles/rc-scripting/_index.po index 8600e08d60..4e96555d59 100644 --- a/documentation/content/en/articles/rc-scripting/_index.po +++ b/documentation/content/en/articles/rc-scripting/_index.po @@ -7,7 +7,7 @@ msgid "" msgstr "" "Project-Id-Version: FreeBSD Documentation VERSION\n" -"POT-Creation-Date: 2024-09-14 15:00-0300\n" +"POT-Creation-Date: 2025-11-08 16:17+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" "Language-Team: LANGUAGE <LL@li.org>\n" @@ -93,8 +93,8 @@ msgid "" "did allow for accessing the network from single-user mode, but it did not " "integrate well into the automatic startup process because parts of its code " "needed to interleave with actions essentially unrelated to networking. That " -"was why [.filename]#/etc/netstart# mutated into [.filename]#/etc/rc." -"network#. The latter was no longer an ordinary script; it comprised of " +"was why [.filename]#/etc/netstart# mutated into [.filename]#/etc/" +"rc.network#. The latter was no longer an ordinary script; it comprised of " "large, tangled man:sh[1] functions called from [.filename]#/etc/rc# at " "different stages of system startup. However, as the startup tasks grew " "diverse and sophisticated, the \"quasi-modular\" approach became even more " @@ -122,8 +122,8 @@ msgid "" "__code reuse__. _Fine modularity_ means that each basic \"service\" such as " "a system daemon or primitive startup task gets its own man:sh[1] script able " "to start the service, stop it, reload it, check its status. A particular " -"action is chosen by the command-line argument to the script. The [." -"filename]#/etc/rc# script still drives system startup, but now it merely " +"action is chosen by the command-line argument to the script. The " +"[.filename]#/etc/rc# script still drives system startup, but now it merely " "invokes the smaller scripts one by one with the `start` argument. It is " "easy to perform shutdown tasks as well by running the same set of scripts " "with the `stop` argument, which is done by [.filename]#/etc/rc.shutdown#. " @@ -142,26 +142,26 @@ msgstr "" #: documentation/content/en/articles/rc-scripting/_index.adoc:101 msgid "" "The BSD [.filename]#rc.d# design is described in crossref:rc-" -"scripting[lukem, the original article by Luke Mewburn], and the [." -"filename]#rc.d# components are documented in great detail in crossref:rc-" +"scripting[lukem, the original article by Luke Mewburn], and the " +"[.filename]#rc.d# components are documented in great detail in crossref:rc-" "scripting[manpages, the respective manual pages]. However, it might not " "appear obvious to an [.filename]#rc.d# newbie how to tie the numerous bits " "and pieces together to create a well-styled script for a particular task. " -"Therefore this article will try a different approach to describe [." -"filename]#rc.d#. It will show which features should be used in a number of " -"typical cases, and why. Note that this is not a how-to document because our " -"aim is not at giving ready-made recipes, but at showing a few easy entrances " -"into the [.filename]#rc.d# realm. Neither is this article a replacement for " -"the relevant manual pages. Do not hesitate to refer to them for more formal " -"and complete documentation while reading this article." +"Therefore this article will try a different approach to describe " +"[.filename]#rc.d#. It will show which features should be used in a number " +"of typical cases, and why. Note that this is not a how-to document because " +"our aim is not at giving ready-made recipes, but at showing a few easy " +"entrances into the [.filename]#rc.d# realm. Neither is this article a " +"replacement for the relevant manual pages. Do not hesitate to refer to them " +"for more formal and complete documentation while reading this article." msgstr "" #. type: Plain text #: documentation/content/en/articles/rc-scripting/_index.adoc:105 msgid "" "There are prerequisites to understanding this article. First of all, you " -"should be familiar with the man:sh[1] scripting language to master [." -"filename]#rc.d#. In addition, you should know how the system performs " +"should be familiar with the man:sh[1] scripting language to master " +"[.filename]#rc.d#. In addition, you should know how the system performs " "userland startup and shutdown tasks, which is described in man:rc[8]." msgstr "" @@ -372,15 +372,15 @@ msgid "" "particular, `start`, `stop`, and other arguments to an [.filename]#rc.d# " "script are handled this way. A method is a man:sh[1] expression stored in a " "variable named `argument_cmd`, where _argument_ corresponds to what can be " -"specified on the script's command line. We will see later how man:rc." -"subr[8] provides default methods for the standard arguments." +"specified on the script's command line. We will see later how " +"man:rc.subr[8] provides default methods for the standard arguments." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/rc-scripting/_index.adoc:209 msgid "" -"To make the code in [.filename]#rc.d# more uniform, it is common to use " -"`${name}` wherever appropriate. Thus a number of lines can be just copied " +"To make the code in [.filename]#rc.d# more uniform, it is common to use `$" +"{name}` wherever appropriate. Thus a number of lines can be just copied " "from one script to another." msgstr "" @@ -411,9 +411,9 @@ msgstr "" #: documentation/content/en/articles/rc-scripting/_index.adoc:224 msgid "" "➐ This call to man:rc.subr[8] loads man:rc.conf[5] variables. Our " -"script makes no use of them yet, but it still is recommended to load man:rc." -"conf[5] because there can be man:rc.conf[5] variables controlling man:rc." -"subr[8] itself." +"script makes no use of them yet, but it still is recommended to load " +"man:rc.conf[5] because there can be man:rc.conf[5] variables controlling " +"man:rc.subr[8] itself." msgstr "" #. type: Plain text @@ -433,8 +433,8 @@ msgstr "" #. type: Plain text #: documentation/content/en/articles/rc-scripting/_index.adoc:239 msgid "" -"Now let us add some controls to our dummy script. As you may know, [." -"filename]#rc.d# scripts are controlled with man:rc.conf[5]. Fortunately, " +"Now let us add some controls to our dummy script. As you may know, " +"[.filename]#rc.d# scripts are controlled with man:rc.conf[5]. Fortunately, " "man:rc.subr[8] hides all the complications from us. The following script " "uses man:rc.conf[5] via man:rc.subr[8] to see whether it is enabled in the " "first place, and to fetch a message to show at boot time. These two tasks " @@ -602,8 +602,8 @@ msgstr "" msgid "" "As a rule, [.filename]#rc.d# scripts of the base system need not provide " "defaults for their man:rc.conf[5] variables because the defaults should be " -"set in [.filename]#/etc/defaults/rc.conf# instead. On the other hand, [." -"filename]#rc.d# scripts for ports should provide the defaults as shown in " +"set in [.filename]#/etc/defaults/rc.conf# instead. On the other hand, " +"[.filename]#rc.d# scripts for ports should provide the defaults as shown in " "the example." msgstr "" @@ -721,12 +721,12 @@ msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/rc-scripting/_index.adoc:378 msgid "" -"Of course, man:sh[1] will permit you to set `${name}_program` from man:rc." -"conf[5] or the script itself even if `command` is unset. In that case, the " -"special properties of `${name}_program` are lost, and it becomes an ordinary " -"variable your script can use for its own purposes. However, the sole use of " -"`${name}_program` is discouraged because using it together with `command` " -"became an idiom of [.filename]#rc.d# scripting." +"Of course, man:sh[1] will permit you to set `${name}_program` from " +"man:rc.conf[5] or the script itself even if `command` is unset. In that " +"case, the special properties of `${name}_program` are lost, and it becomes " +"an ordinary variable your script can use for its own purposes. However, the " +"sole use of `${name}_program` is discouraged because using it together with " +"`command` became an idiom of [.filename]#rc.d# scripting." msgstr "" #. type: Plain text @@ -1007,8 +1007,8 @@ msgid "" "commands and shell functions are not always the same thing. For instance, " "`xyzzy` is not implemented as a function here. In addition, there can be a " "pre-command and post-command, which should be invoked orderly. So the " -"proper way for a script to run its own command is by means of man:rc." -"subr[8], as shown in the example." +"proper way for a script to run its own command is by means of " +"man:rc.subr[8], as shown in the example." msgstr "" #. type: Plain text @@ -1109,15 +1109,16 @@ msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/rc-scripting/_index.adoc:594 msgid "" -"After a script has been written, it needs to be integrated into [." -"filename]#rc.d#. The crucial step is to install the script in [.filename]#/" -"etc/rc.d# (for the base system) or [.filename]#/usr/local/etc/rc.d# (for " -"ports). Both [.filename]#bsd.prog.mk# and [.filename]#bsd.port.mk# provide " -"convenient hooks for that, and usually you do not have to worry about the " -"proper ownership and mode. System scripts should be installed from [." -"filename]#src/libexec/rc/rc.d# through the [.filename]#Makefile# found " -"there. Port scripts can be installed using `USE_RC_SUBR` as described " -"extref:{porters-handbook}[in the Porter's Handbook, rc-scripts]." +"After a script has been written, it needs to be integrated into " +"[.filename]#rc.d#. The crucial step is to install the script in " +"[.filename]#/etc/rc.d# (for the base system) or [.filename]#/usr/local/etc/" +"rc.d# (for ports). Both [.filename]#bsd.prog.mk# and " +"[.filename]#bsd.port.mk# provide convenient hooks for that, and usually you " +"do not have to worry about the proper ownership and mode. System scripts " +"should be installed from [.filename]#src/libexec/rc/rc.d# through the " +"[.filename]#Makefile# found there. Port scripts can be installed using " +"`USE_RC_SUBR` as described extref:{porters-handbook}special[in the Porter's " +"Handbook, rc-scripts]." msgstr "" #. type: delimited block = 4 @@ -1170,9 +1171,9 @@ msgstr "" #: documentation/content/en/articles/rc-scripting/_index.adoc:615 msgid "" "It is no surprise that man:rcorder[8] can handle only text files with a " -"syntax close to that of man:sh[1]. That is, special lines understood by man:" -"rcorder[8] look like man:sh[1] comments. The syntax of such special lines " -"is rather rigid to simplify their processing. See man:rcorder[8] for " +"syntax close to that of man:sh[1]. That is, special lines understood by " +"man:rcorder[8] look like man:sh[1] comments. The syntax of such special " +"lines is rather rigid to simplify their processing. See man:rcorder[8] for " "details." msgstr "" @@ -1256,21 +1257,21 @@ msgstr "" #: documentation/content/en/articles/rc-scripting/_index.adoc:666 msgid "" "➋➌ So our script indicates which \"conditions\" provided by " -"other scripts it depends on. According to the lines, our script asks man:" -"rcorder[8] to put it after the script(s) providing [.filename]#DAEMON# and [." -"filename]#cleanvar#, but before that providing [.filename]#LOGIN#." +"other scripts it depends on. According to the lines, our script asks " +"man:rcorder[8] to put it after the script(s) providing [.filename]#DAEMON# " +"and [.filename]#cleanvar#, but before that providing [.filename]#LOGIN#." msgstr "" #. type: delimited block = 4 #: documentation/content/en/articles/rc-scripting/_index.adoc:672 msgid "" "The `BEFORE:` line should not be abused to work around an incomplete " -"dependency list in the other script. The appropriate case for using `BEFORE:" -"` is when the other script does not care about ours, but our script can do " -"its task better if run before the other one. A typical real-life example is " -"the network interfaces vs. the firewall: While the interfaces do not depend " -"on the firewall in doing their job, the system security will benefit from " -"the firewall being ready before there is any network traffic." +"dependency list in the other script. The appropriate case for using " +"`BEFORE:` is when the other script does not care about ours, but our script " +"can do its task better if run before the other one. A typical real-life " +"example is the network interfaces vs. the firewall: While the interfaces do " +"not depend on the firewall in doing their job, the system security will " +"benefit from the firewall being ready before there is any network traffic." msgstr "" #. type: delimited block = 4 @@ -1278,9 +1279,9 @@ msgstr "" msgid "" "Besides conditions corresponding to a single service each, there are meta-" "conditions and their \"placeholder\" scripts used to ensure that certain " -"groups of operations are performed before others. These are denoted by [." -"filename]#UPPERCASE# names. Their list and purposes can be found in man:" -"rc[8]." +"groups of operations are performed before others. These are denoted by " +"[.filename]#UPPERCASE# names. Their list and purposes can be found in " +"man:rc[8]." msgstr "" #. type: delimited block = 4 @@ -1288,11 +1289,11 @@ msgstr "" msgid "" "Keep in mind that putting a service name in the `REQUIRE:` line does not " "guarantee that the service will actually be running by the time our script " -"starts. The required service may fail to start or just be disabled in man:" -"rc.conf[5]. Obviously, man:rcorder[8] cannot track such details, and man:" -"rc[8] will not do that either. Consequently, the application started by our " -"script should be able to cope with any required services being unavailable. " -"In certain cases, we can help it as discussed crossref:rc-" +"starts. The required service may fail to start or just be disabled in " +"man:rc.conf[5]. Obviously, man:rcorder[8] cannot track such details, and " +"man:rc[8] will not do that either. Consequently, the application started by " +"our script should be able to cope with any required services being " +"unavailable. In certain cases, we can help it as discussed crossref:rc-" "scripting[forcedep, below]" msgstr "" @@ -1300,20 +1301,20 @@ msgstr "" #: documentation/content/en/articles/rc-scripting/_index.adoc:687 msgid "" "[[keywords]]➍ As we remember from the above text, man:rcorder[8] " -"keywords can be used to select or leave out some scripts. Namely any man:" -"rcorder[8] consumer can specify through `-k` and `-s` options which keywords " -"are on the \"keep list\" and \"skip list\", respectively. From all the " -"files to be dependency sorted, man:rcorder[8] will pick only those having a " -"keyword from the keep list (unless empty) and not having a keyword from the " -"skip list." +"keywords can be used to select or leave out some scripts. Namely any " +"man:rcorder[8] consumer can specify through `-k` and `-s` options which " +"keywords are on the \"keep list\" and \"skip list\", respectively. From all " +"the files to be dependency sorted, man:rcorder[8] will pick only those " +"having a keyword from the keep list (unless empty) and not having a keyword " +"from the skip list." msgstr "" #. type: Plain text #: documentation/content/en/articles/rc-scripting/_index.adoc:690 msgid "" "In FreeBSD, man:rcorder[8] is used by [.filename]#/etc/rc# and [.filename]#/" -"etc/rc.shutdown#. These two scripts define the standard list of FreeBSD [." -"filename]#rc.d# keywords and their meanings as follows:" +"etc/rc.shutdown#. These two scripts define the standard list of FreeBSD " +"[.filename]#rc.d# keywords and their meanings as follows:" msgstr "" #. type: Labeled list @@ -1339,8 +1340,8 @@ msgstr "" #: documentation/content/en/articles/rc-scripting/_index.adoc:697 msgid "" "The service is to be started manually or not started at all. The automatic " -"startup procedure will ignore the script. In conjunction with the [." -"filename]#shutdown# keyword, this can be used to write scripts that do " +"startup procedure will ignore the script. In conjunction with the " +"[.filename]#shutdown# keyword, this can be used to write scripts that do " "something only at system shutdown." msgstr "" @@ -1362,13 +1363,13 @@ msgstr "" msgid "" "When the system is going to shut down, [.filename]#/etc/rc.shutdown# runs. " "It assumes that most [.filename]#rc.d# scripts have nothing to do at that " -"time. Therefore [.filename]#/etc/rc.shutdown# selectively invokes [." -"filename]#rc.d# scripts with the [.filename]#shutdown# keyword, effectively " -"ignoring the rest of the scripts. For even faster shutdown, [.filename]#/" -"etc/rc.shutdown# passes the [.filename]#faststop# command to the scripts it " -"runs so that they skip preliminary checks, e.g., the pidfile check. As " -"dependent services should be stopped before their prerequisites, [." -"filename]#/etc/rc.shutdown# runs the scripts in reverse dependency order. " +"time. Therefore [.filename]#/etc/rc.shutdown# selectively invokes " +"[.filename]#rc.d# scripts with the [.filename]#shutdown# keyword, " +"effectively ignoring the rest of the scripts. For even faster shutdown, " +"[.filename]#/etc/rc.shutdown# passes the [.filename]#faststop# command to " +"the scripts it runs so that they skip preliminary checks, e.g., the pidfile " +"check. As dependent services should be stopped before their prerequisites, " +"[.filename]#/etc/rc.shutdown# runs the scripts in reverse dependency order. " "If writing a real [.filename]#rc.d# script, you should consider whether it " "is relevant at system shutdown time. E.g., if your script does its work in " "response to the [.filename]#start# command only, then you need not to " @@ -1413,8 +1414,8 @@ msgstr "" #: documentation/content/en/articles/rc-scripting/_index.adoc:736 msgid "" "When invoked during startup or shutdown, an [.filename]#rc.d# script is " -"supposed to act on the entire subsystem it is responsible for. E.g., [." -"filename]#/etc/rc.d/netif# should start or stop all network interfaces " +"supposed to act on the entire subsystem it is responsible for. E.g., " +"[.filename]#/etc/rc.d/netif# should start or stop all network interfaces " "described by man:rc.conf[5]. Either task can be uniquely indicated by a " "single command argument such as `start` or `stop`. Between startup and " "shutdown, [.filename]#rc.d# scripts help the admin to control the running " @@ -1440,9 +1441,9 @@ msgstr "" msgid "" "How can man:rc.subr[8] gain access to the extra command-line arguments. " "Should it just grab them directly? Not by any means. Firstly, an man:sh[1] " -"function has no access to the positional parameters of its caller, but man:" -"rc.subr[8] is just a sack of such functions. Secondly, the good manner of [." -"filename]#rc.d# dictates that it is for the main script to decide which " +"function has no access to the positional parameters of its caller, but " +"man:rc.subr[8] is just a sack of such functions. Secondly, the good manner " +"of [.filename]#rc.d# dictates that it is for the main script to decide which " "arguments are to be passed to its methods." msgstr "" @@ -1662,9 +1663,8 @@ msgstr "" #. type: Plain text #: documentation/content/en/articles/rc-scripting/_index.adoc:856 msgid "" -"To make a script ready for use with extref:../../books/handbook/jails/" -"#service-jails[Service Jails], only one more config line needs to be " -"inserted:" +"To make a script ready for use with extref:{handbook}jails[Service Jails, " +"service-jails], only one more config line needs to be inserted:" msgstr "" #. type: delimited block . 4 @@ -1839,10 +1839,10 @@ msgstr "" #. type: Plain text #: documentation/content/en/articles/rc-scripting/_index.adoc:978 msgid "" -"➊ and ➋ make sure to set the name variable to the man:" -"basename[1] of the script name. If the filename is [.filename]#/usr/local/" -"etc/rc.d/dummy#, name is set to [.filename]#dummy#. This way changing the " -"filename of the rc script changes automatically the content of the name " +"➊ and ➋ make sure to set the name variable to the " +"man:basename[1] of the script name. If the filename is [.filename]#/usr/" +"local/etc/rc.d/dummy#, name is set to [.filename]#dummy#. This way changing " +"the filename of the rc script changes automatically the content of the name " "variable." msgstr "" @@ -1906,8 +1906,8 @@ msgid "" "The above creates an instance of the dummy service with the name dummy_foo. " "It does not use the config file [.filename]#/usr/local/etc/dummy.cfg# but " "the config file [.filename]#/usr/local/etc/dummy_foo.cfg# (➐), and it " -"uses the PID file [.filename]#/var/run/dummy/dummy_foo.pid# instead of [." -"filename]#/var/run/dummy/dummy.pid#." +"uses the PID file [.filename]#/var/run/dummy/dummy_foo.pid# instead of " +"[.filename]#/var/run/dummy/dummy.pid#." msgstr "" #. type: Plain text @@ -1933,8 +1933,8 @@ msgstr "" msgid "" "[[lukem]]http://www.mewburn.net/luke/papers/rc.d.pdf[The original article by " "Luke Mewburn] offers a general overview of [.filename]#rc.d# and detailed " -"rationale for its design decisions. It provides insight on the whole [." -"filename]#rc.d# framework and its place in a modern BSD operating system." +"rationale for its design decisions. It provides insight on the whole " +"[.filename]#rc.d# framework and its place in a modern BSD operating system." msgstr "" #. type: Plain text |