|Activate entry nr <n> at startup|
The color a logfile button should flash to when an alert has been
triggered for this particular logfile. The color is in GTK+ standard,
this means values between 0 and 1 for red,green,blue.
Example: A commandline option of -alertcolor 0,1.0,0 would mean that the button will flash bright green.
IMPORTANT: While values have to be seperated by a comma, the values themselves have to be given with a decimal point (so 0.45 and NOT 0,45 for instance).
|Generally turns audio support for the xlogmaster on/off. For audio support you must have the OSS installed (/dev/dsp must exist).|
Selects file to play whenever an "alert" filter has been triggered
(see tutorial). The file must be playable via "cat filename >
/dev/dsp" ( about 8KHz and a standard (WAVE, ULaw...) format ).
If you give "off" as the filename, there will be no sound for alert events.
|Same as "-audio-alert", only for "notice" events (see tutorial).|
|Same as "-audio-alert", only for "uniconify" events (see tutorial).|
|Set the size of the buffered text to <n>[bytes/kilobytes/megabytes]. This gives the maximum number of bytes that can be reviewed at any point.|
|Use <file> as the config file for Xlogmaster|
|Use <directory> for the logfile database, overrides default & environment variable|
|Amount of seconds it takes an alert-highlighted button to fade back to normal. Something like 300 seconds is usually a good value.|
|Number of steps taken when fading back from alertcolor to standard background color of a button. Depending on how different the colors are and how fast you letthe buttons fade back something between 20 and 200 should be a sane value.|
|Standard X11 geometry statement|
|Use <file> as the GTK+ rc file (controlling the color selection & look). See GTK+ toolkit for details.|
|-help||Prints short help message and exits.|
Try to lock the pages of the Xlogmaster in memory so they dont get
This function is meant for admins of machines with heavy memory usage and logfiles that are considered extremely important (like some servers). It *only* works on machines that support the mlockall() call and usually *only for root*. If the system allows locking and you use more memory pages than the system likes to see locked a segfault is pretty likely. This is definitely something that has to be called a superuser feature !
Usual users could request the locking but nothing would happen. You could of course make the xlogmaster suid root, but *I TELL YOU: DONT !!!!!!!* You would allow everyone who could start it to save the xlogmaster configuration over anything - even the kernel image, for instance. The only clean way is probably a little wrapper that only you have access to and if you dont know how to set that up you definitely dont know enough to use this feature. Most people wont need it, anyways - so once again: USE WITH EXTREME CAUTION AND ONLY IF YOU KNOW WHAT YOU ARE DOING ! THIS IS A SUPERUSER FEATURE !
Determines whether the notice box (see Class1 filters in tutorial)
should follow the mouse around. This doesnt mean the notice dialog
sticks to the mouse pointer, it rather lets the notice box move to
the current mouse position every time a new entry is added to the
Since most people will probably find it annoying this feature is disabled as the default.
|-silent||Same as "-audio off".|
|If set to yes Xlogmaster will use a standard 64x64 pixel icon instead of the logo for iconify.|
|-terse||Assume user knows what hes doing - no "are you sure ?" questions for possibly critical tasks like leaving the Xlogmaster.|
|-version||Prints version information and exits.|
|Should the words be cut in half or wrapped properly ? Give yes for proper wrapping.|
Send all bug reports to:
Xlogmaster was written by Georg C. F. Greve.
Copyright (C) 1998 by Georg C. F. Greve <email@example.com> This file is part of GNU xlogmaster.
GNU xlogmaster is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
GNU xlogmaster is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.