IPTOTALD(8) System Manager's Manual IPTOTALD(8)NAME
iptotald - iptotal daemon
SYNOPSIS
iptotald
DESCRIPTION
iptotald is the daemon program for iptotal.
iptotal is the daemon that regularly invokes iptotal(8) to monitor traffic. It is normally started at boot from /etc/rc.
OPTIONS
None.
CONFIGURATION FILE
/etc/iptotal.conf
File that defines the configuration used to invoke iptotal(8). See iptotal_config(5) for more details.
AUTHOR
Written by Antoine Megens <webmaster@dingetje.homeip.net>
Manpage written by Millis Miller <millis@faztek.org>
REPORTING BUGS
Report bugs to <webmaster@dingetje.homeip.net>
COPYRIGHT
Copyright (C) 2003, 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO iptotal(1), iptotal_config(5), rrdtool(1)iptotal 0.3.3 Jun 2004 IPTOTALD(8)
Check Out this Related Man Page
SUXTERM(1) User Commands SUXTERM(1)NAME
sux - wrapper around su which will transfer your X credentials
SYNOPSIS
sux [OPTS] [-] [username] [ARGS]]
suxterm [OPTS] [-] [username]
DESCRIPTION
sux is a wrapper around the standard su command which will transfer your X credentials to the target user.
Note, suxterm forces ARGS to be 'xterm', and will try to launch an xterminal window.
QUICK CALLING
'sux user' and 'sux - user' behave just like su but transfer $DISPLAY and the X cookies.
OPTIONS --untrusted
To generate an untrusted cookie, see 'xauth'.
--timeout <period>
To generate a temporary cookie for <period> seconds, see 'xauth'.
-m,-p --preserve-environment
In this case sux will override XAUTHORITY to the so that xauth does not try to use the original user's .Xauthority file (which it
obviously could not do anyway due to access rights).
--no-cookies
Just transfer DISPLAY, not the cookies. You could do this if you have already transfered the cookies in a previous invocation of
sux.
--copy-cookies
Copy the cookies using xauth. This is the default method (and only method most of the time).
--use-xauthority
Instead of transferring the cookies, set the XAUTHORITY environment variable to access the original .Xauthority file. There's a
couple caveats with this method. First, due to the access right issues it's only usable by root. But even then it may not work if
the .Xauthority file is accessed via NFS, e.g. if the home directories are on NFS (note that this is quite dangerous already since
your cookies will travel unencrypted over the network). Then, if root runs commands like xauth add/remove, the .Xauthority's owner-
ship will belong to him. This will leave the original user in trouble as he will no longer be able to access X! So only use this
option with great care. Finally, this method does not work if you also want to use '--untrusted' or '--timeout'.
--display
specify which display to use (in case of having more than one available).
AUTHOR
Originally written by Francois Gouget <fgouget@free.fr> Manpage written by Millis Miller <millis@faztek.org>
REPORTING BUGS
Report bugs to <millis@faztek.org>.
COPYRIGHT
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU-
LAR PURPOSE.
SEE ALSO
su (1), xauth (1)
sux 1.0 Sept 2003 SUXTERM(1)