summaryrefslogtreecommitdiff
path: root/docs/oc/oc.po
diff options
context:
space:
mode:
authorRay Strode <rstrode@redhat.com>2015-10-27 15:56:04 -0400
committerRay Strode <rstrode@redhat.com>2015-10-27 15:56:04 -0400
commit1c78f2dfccea17fe377349cbc74326e01347283e (patch)
treeda62dde3f3e3568f92275200c31781633bc914c2 /docs/oc/oc.po
parent755565a16ed914af4ab59529e385c29fec077e74 (diff)
downloadgdm-1c78f2dfccea17fe377349cbc74326e01347283e.tar.gz
get rid of references to slaves
I really don't want $ git grep slave to return hits.
Diffstat (limited to 'docs/oc/oc.po')
-rw-r--r--docs/oc/oc.po121
1 files changed, 0 insertions, 121 deletions
diff --git a/docs/oc/oc.po b/docs/oc/oc.po
index f6e0f88d..e0234621 100644
--- a/docs/oc/oc.po
+++ b/docs/oc/oc.po
@@ -356,22 +356,6 @@ msgid ""
"discussed further in the next section."
msgstr ""
-#: ../C/gdm.xml:248(para)
-msgid ""
-"When the GDM daemon is asked to manage a display, it will fork an X server "
-"process, then run the <filename>Init</filename> script as the root user, and "
-"start the login GUI dialog as a slave process on the display. GDM can be "
-"configured to use either <command>gdmgreeter</command> (the default) or "
-"<command>gdmlogin</command> as the GUI dialog program. The "
-"<command>gdmlogin</command> program supports accessibility while the "
-"<command>gdmgreeter</command> program supports greater themeability. The GUI "
-"dialog is run as the unpriviledged \"gdm\" user/group which is described in "
-"the \"Security\" section below. The GUI dialog communicates with the daemon "
-"via a sockets protocol and via standard input/output. The slave, for example "
-"passes the username and password information to the GDM daemon via standard "
-"input/output so the daemon can handle the actual authentication."
-msgstr ""
-
#: ../C/gdm.xml:265(para)
msgid ""
"The login GUI dialog screen allows the user to select which session they "
@@ -387,23 +371,6 @@ msgid ""
"(after entering the root password)."
msgstr ""
-#: ../C/gdm.xml:280(para)
-msgid ""
-"GDM, by default, will use Pluggable Authentication Modules (PAM) for "
-"authentication, but can also support regular crypt and shadow passwords on "
-"legacy systems. After authenticating a user, the daemon runs the "
-"<filename>PostLogin</filename> script as root, and forks a slave process to "
-"start the requested session. This slave process runs the "
-"<filename>PreSession</filename> script as root, sets up the user's "
-"environment, and starts the requested session. GDM keeps track of the user's "
-"default session and language in the user's <filename>~/.dmrc</filename> and "
-"will use these defaults if the user did not pick a session or language in "
-"the login GUI. On Solaris, GDM (since version 2.8.0.3) uses the SDTLOGIN "
-"interface after user authentication to tell the X server to be restarted as "
-"the user instead of as root for added security. When the user's session "
-"exits, the GDM daemon will run the <filename>PostSession</filename> script "
-"as root."
-msgstr ""
#: ../C/gdm.xml:297(para)
msgid ""
@@ -994,16 +961,6 @@ msgid ""
"is not appropriate for gdm."
msgstr ""
-#: ../C/gdm.xml:879(para)
-msgid ""
-"The GDM daemon normally runs as root, as does the slave. However GDM should "
-"also have a dedicated user id and a group id which it uses for its graphical "
-"interfaces such as <command>gdmgreeter</command> and <command>gdmlogin</"
-"command>. These are configured via the <filename>User</filename> and "
-"<filename>Group</filename> configuration options in the GDM configuration "
-"files. The user and group should be created before running \"make install\". "
-"By default GDM assumes the user and the group are called \"gdm\"."
-msgstr ""
#: ../C/gdm.xml:890(para)
msgid ""
@@ -1778,20 +1735,6 @@ msgid ""
"is not set."
msgstr ""
-#: ../C/gdm.xml:1641(para)
-msgid ""
-"When the user terminates his session, the <filename>PostSession</filename> "
-"script will be run. Again operation is similar to <filename>Init</filename>, "
-"<filename>PostLogin</filename> and <filename>PreSession</filename>. Again "
-"the script will be run with root privileges, the slave daemon will block and "
-"the <filename>$USER</filename> environment variable will contain the name of "
-"the user who just logged out and <filename>$DISPLAY</filename> will be set "
-"to the display the user used, however note that the X server for this "
-"display may already be dead and so you shouldn't try to access it. Also "
-"<filename>$X_SERVERS</filename> environmental variable is set and this "
-"points to a fake generated X servers file for use with the sessreg "
-"accounting application."
-msgstr ""
#: ../C/gdm.xml:1656(para)
msgid ""
@@ -4989,18 +4932,6 @@ msgstr ""
msgid "handled=true"
msgstr ""
-#: ../C/gdm.xml:4376(para)
-msgid ""
-"Indicates that GDM should run the login window on this server and allow a "
-"user to log in. If set to false, then GDM will just run this server and wait "
-"for it to terminate. This can be useful to run an X terminal using GDM. When "
-"this is done you should normally also add <filename>-terminate</filename> to "
-"the command line of the server to make the server terminate after each "
-"session. Otherwise the control of the slave will never come back to GDM and, "
-"for example, soft restarts won't work. This is because GDM assumes there is "
-"a login in progress for the entire time this server is active."
-msgstr ""
-
#: ../C/gdm.xml:4392(term)
msgid "chooser"
msgstr ""
@@ -5249,16 +5180,6 @@ msgid ""
"application)."
msgstr ""
-#: ../C/gdm.xml:4629(para)
-msgid ""
-"Full and up to date documentation of the commands and their use is contained "
-"in the GDM source tree in the file <filename>daemon/gdm.h</filename>. Look "
-"for the defines starting with <filename>GDM_SOP_</filename>. The commands "
-"which require the pid of the slave as an argument are the ones that are "
-"really used for internal communication of the slave with the master and "
-"should not be used."
-msgstr ""
-
#: ../C/gdm.xml:4641(title)
msgid "Socket Protocol"
msgstr ""
@@ -5895,52 +5816,10 @@ msgstr ""
msgid "SERVER_BUSY"
msgstr ""
-#: ../C/gdm.xml:5185(screen)
-#, no-wrap
-msgid ""
-"\n"
-"SERVER_BUSY: Returns true if half or more of the daemon's sockets\n"
-" are busy, false otherwise. Used by slave programs\n"
-" which want to ensure they do not overwhelm the \n"
-" sever.\n"
-"Supported since: 2.13.0.8\n"
-"Arguments: None\n"
-"Answers:\n"
-" OK &lt;value&gt;\n"
-" ERROR &lt;err number&gt; &lt;english error description&gt;\n"
-" 0 = Not implemented\n"
-" 200 = Too many messages\n"
-" 999 = Unknown error\n"
-msgstr ""
-
#: ../C/gdm.xml:5202(title)
msgid "SET_LOGOUT_ACTION"
msgstr ""
-#: ../C/gdm.xml:5203(screen)
-#, no-wrap
-msgid ""
-"\n"
-"SET_LOGOUT_ACTION: Tell the daemon to halt/restart/suspend after\n"
-" slave process exits. Only supported on\n"
-" connections that passed AUTH_LOCAL.\n"
-"Supported since: 2.5.90.0\n"
-"Arguments: &lt;action&gt;\n"
-" NONE Set exit action to 'none'\n"
-" HALT Set exit action to 'halt'\n"
-" REBOOT Set exit action to 'reboot'\n"
-" SUSPEND Set exit action to 'suspend'\n"
-" CUSTOM_CMD[0-9] Set exit action to 'custom command [0-9]'\n"
-"Answers:\n"
-" OK\n"
-" ERROR &lt;err number&gt; &lt;english error description&gt;\n"
-" 0 = Not implemented\n"
-" 7 = Unknown logout action, or not available\n"
-" 100 = Not authenticated\n"
-" 200 = Too many messages\n"
-" 999 = Unknown error\n"
-msgstr ""
-
#: ../C/gdm.xml:5226(title)
msgid "SET_SAFE_LOGOUT_ACTION"
msgstr ""