From 20f5c9875f3c2648f75b23e376ac43442f75a7f6 Mon Sep 17 00:00:00 2001 From: "Martin A. Brown" Date: Thu, 3 Mar 2016 12:06:19 -0800 Subject: [PATCH] putting indexterms inside their or tags --- LDP/guide/docbook/Intro-Linux/chap3.xml | 2 +- LDP/guide/docbook/Intro-Linux/chap4.xml | 2 +- LDP/guide/docbook/Intro-Linux/chap5.xml | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/LDP/guide/docbook/Intro-Linux/chap3.xml b/LDP/guide/docbook/Intro-Linux/chap3.xml index 565fd545..bae2d759 100644 --- a/LDP/guide/docbook/Intro-Linux/chap3.xml +++ b/LDP/guide/docbook/Intro-Linux/chap3.xml @@ -695,7 +695,7 @@ Diskquotas for user pierre (uid 501): none The most common variable files -In the /varvar directory we find a set of directories for storing specific non-constant data (as opposed to the ls program or the system configuration files, which change relatively infrequently or never at all). All files that change frequentlyvariable filesoverview, such as log files, mailboxes, lock files, spoolers etc. are kept in a subdirectory of /var. +In the /varvar directory we find a set of directories for storing specific non-constant data (as opposed to the ls program or the system configuration files, which change relatively infrequently or never at all). All files that change frequentlyvariable filesoverview, such as log files, mailboxes, lock files, spoolers etc. are kept in a subdirectory of /var. As a security measure these files are usually kept in separate parts from the main system files, so we can keep a close eye on them and set stricter permissions where necessary. A lot of these files also need more permissions than usual, like /var/tmptmp, which needs to be writable for everyone. A lot of user activity might be expected here, which might even be generated by anonymous Internet users connected to your system. This is one reason why the /var directorypartitionsvar partition, including all its subdirectories, is usually on a separate partition. This way, there is for instance no risk that a mail bomb, for instance, fills up the rest of the file system, containing more important data such as your programs and configuration files. /var/tmp and /tmp Files in /tmptemporary files can be deleted without notice, by regular system tasks or because of a system reboot. On some (customized) systems, also /var/tmp might behave unpredictably. Nevertheless, since this is not the case by default, we advise to use the /var/tmp directory for saving temporary files. When in doubt, check with your system administrator. If you manage your own system, you can be reasonably sure that this is a safe place if you did not consciously change settings on /var/tmp (as root, a normal user can not do this). diff --git a/LDP/guide/docbook/Intro-Linux/chap4.xml b/LDP/guide/docbook/Intro-Linux/chap4.xml index b229ba43..c07954ba 100644 --- a/LDP/guide/docbook/Intro-Linux/chap4.xml +++ b/LDP/guide/docbook/Intro-Linux/chap4.xml @@ -310,7 +310,7 @@ passwd is /usr/bin/passwd -r-s--x--x 1 root root 13476 Aug 7 06:03 /usr/bin/passwd* When called, the passwd command will run using the access permissionsfile permissionsSUID of root, thus enabling a common user to edit the password file which is owned by the system admin. -SGID modes on a file don't occur nearly as frequently as SUID, because SGID often involves the creation of extra groups. In some cases, however, we have to go through this trouble in order to build an elegant solution (don't worry about this too much - the necessary groups are usually created upon installation). This is the case for the writewrite4dwx and wallwall programs, which are used to send messages to other users' terminalsterminalsend a message (ttys). The write command writes a message to a single user, while wall writes to all connected users. +SGID modes on a file don't occur nearly as frequently as SUID, because SGID often involves the creation of extra groups. In some cases, however, we have to go through this trouble in order to build an elegant solution (don't worry about this too much - the necessary groups are usually created upon installation). This is the case for the writewrite4dwx and wallwall programs, which are used to send messages to other users' terminalsterminalsend a message (ttys). The write command writes a message to a single user, while wall writes to all connected users. Sending text to another user's terminal or graphical display is normally not allowed. In order to bypass this problem, a group has been created, which owns all terminal devices. When the write and wall commands are granted SGID permissions, the commands will run using the access rights as applicable to this group, tty in the example. Since this group has write access to the destination terminal, also a user having no permissions to use that terminal in any way can send messages to it. In the example below, user joe first finds out on which terminal his correspondent is connected, using the who command. Then he sends her a message using the write command. Also illustrated are the access rights on the write program and on the terminals occupied by the receiving user: it is clear that others than the user owner have no permissionsfile permissionsSGID on the device, except for the group owner, which can write to it. diff --git a/LDP/guide/docbook/Intro-Linux/chap5.xml b/LDP/guide/docbook/Intro-Linux/chap5.xml index 3fa5f955..f3da515c 100644 --- a/LDP/guide/docbook/Intro-Linux/chap5.xml +++ b/LDP/guide/docbook/Intro-Linux/chap5.xml @@ -306,8 +306,8 @@ My boss grep root /etc/passwd /etc/nofiles > grepresults /etc/init.d/sshd start > /var/tmp/output /etc/init.d/crond start > /var/tmp/output 2>&1 -Now check your results by issuing the commands again, now redirecting standardoutput to the file /var/tmp/output and standard error to the file /var/tmp/error. +Now check your results by issuing the commands again, now redirecting standardoutput to the file /var/tmp/output and standard error to the file /var/tmp/error. How many processes are you currently running?