Linux and UNIX Man Pages

Test Your Knowledge in Computers #652
Difficulty: Easy
Puffy is the mascot of Linux Mint.
True or False?
Linux & Unix Commands - Search Man Pages

syslogout(8) [debian man page]

SYSLOGOUT(8)						      System Manager's Manual						      SYSLOGOUT(8)

NAME
syslogout - modular centralized shell logout mechanism DESCRIPTION
syslogout is a generic approach to enable centralized shell logout actions for all users of a given system in a modular and centralized way mostly aimed at avoiding work for lazy sysadmins. It has only been tested to work with the bash shell. It basically consists of the small /etc/syslogout shell script which invokes other small shell scripts having a .bash suffix which are con- tained in the /etc/syslogout.d/ directory. The system administrator can drop in any script he wants without any naming convention other than that the scripts need to have a .bash suffix to enable automagic sourcing by the /etc/syslogout script. For shell sessions, the contents of /etc/syslogout.d/" will be sourced by every user at logout if the following lines are present in his $HOME/.bash_logout: if [ -f /etc/syslogout ]; then . /etc/syslogout fi If used for X sessions it is advisable to include the former statement into the Xreset script of the X display manager instead to prevent that closing of an terminal emulator window yields unexpected results in your running X session if your X11 terminal emulator is using a login shell. Be sure then to run it under the user-id of the X session's user. See the example files in /usr/share/doc/syslogout/ for illustration. Users not wanting /etc/syslogout to be sourced for their environment can easily disable it's automatic mechanism. It can be disabled by simply creating an empty file called $HOME/.nosyslogout in the user's home directory using e.g. the touch(1) command. Any single configuration file in /etc/syslogout.d/ can simply be overridden by any user by creating a private $HOME/.syslogout.d/ directory which may contain a user's own version of any configuration file to be sourced instead of the system default. It's names have just to match exactly the system's default /etc/syslogout.d/ configuration files. Empty versions of these files contained in the $HOME/.syslo- gout.d/ directory automatically disable sourcing of the system wide version. Naturally, users can add and include their own private scripts to be automagically executed by /etc/syslogout at logout time. OPTIONS
There are no options other than those dictated by shell conventions. Anything is defined within the configuration scripts themselves. SEE ALSO
The README files and configuration examples contained in /usr/share/doc/syslogout/ and the manual page for bash(1), xdm(1x), xdm.options(5), and wdm(1x). Recommended further reading is everything related with shell programming. If you need a similar mechanism for executing code at login time check out the related package sysprofile(8) which is a very close compan- ion to syslogout. BUGS
syslogout in its current form is mainly restricted to bash(1) syntax. In fact it is actually a rather embarrassing quick and dirty hack than anything else - but it works. It serves the practical need to enable a centralized bash configuration until something better becomes available. Your constructive criticism in making this into something better" is very welcome. Before i forget to mention it: we take patches... ;-) AUTHOR
syslogout was developed by Paul Seelig <pseelig@debian.org> specifically for the Debian GNU/Linux system. Feel free to port it to and use it anywhere else under the conditions of either the GNU public license or the BSD license or both. Better yet, please help to make it into something more worthwhile than it currently is. SYSLOGOUT(8)

Check Out this Related Man Page

DEVSCRIPTS.CONF(5)						File Formats Manual						DEVSCRIPTS.CONF(5)

NAME
       devscripts.conf - configuration file for the devscripts package

DESCRIPTION
       The  devscripts	package provides a collection of scripts which may be of use to Debian developers and others wishing to build Debian pack-
       ages.  Many of these have options which can be configured on a system-wide and per-user basis.

       Every script in the devscripts package which makes use of values from these configuration files describes the specific settings	recognised
       in its own manpage.  (For a list of the scripts, either see /usr/share/doc/devscripts/README.gz or look at the output of dpkg -L devscripts
       | grep /usr/bin.)

       The two configuration files are /etc/devscripts.conf for system-wide defaults and ~/.devscripts for per-user settings.	They  are  written
       with  bash(1)  syntax, but should only have comments and simple variable assignments in them; they are both sourced (if present) by many of
       the devscripts scripts.	Variables corresponding to simple switches should have one of the values yes and no; any other setting is regarded
       as equivalent to the default setting.

       All  variable  names  are  written  in  uppercase, and begin with the script name.  Package-wide variables begin with "DEVSCRIPTS", and are
       listed below, as well as in the relevant manpages.

       For a list of  all  of  the  available  options	variables,  along  with  their	default  settings,  see  the  example  configuration  file
       /usr/share/doc/devscripts/devscripts.conf.ex.   This  is  copied  to  /etc/devscripts.conf  when the devscripts package is first installed.
       Information about configuration options introduced in newer versions of the package will be appended to /etc/devscripts.conf when the pack-
       age is upgraded.

       Every script which reads the configuration files can be forced to ignore them by using --no-conf as the first command-line option.

PACKAGE-WIDE VARIABLES
       The currently recognised package-wide variables are:

       DEVSCRIPTS_CHECK_DIRNAME_LEVEL, DEVSCRIPTS_CHECK_DIRNAME_REGEX
	      These  variables	control  scripts  which change directory to find a debian/changelog file or suchlike, and some other miscellaneous
	      cases.  In order to prevent unwanted, even possibly dangerous, behaviour, these variables control when actions  will  be	performed.
	      The scripts which currently make use of these variables are: debc, debchange/dch, debclean, debi, debrelease, debuild and uscan, but
	      this list may change with time (and I may not remember to update this manpage).  Please see the manpages of individual  scripts  for
	      details of the specific behaviour for each script.

SEE ALSO
       devscripts(1) and /usr/share/doc/devscripts/README.gz.

AUTHOR
       This manpage was written for the devscripts package by the package maintainer Julian Gilbey <jdg@debian.org>.

DEBIAN								 Debian Utilities						DEVSCRIPTS.CONF(5)

Featured Tech Videos