DESCRIPTIONYou know when you have been having your signature for too long, then it needs replacement, but what if you get tired of manualy having to come up with alot of new signatures all the time. These problems are no longer required, sigit will handle it for you. You decide how long you like to wait, untill the signature is changed, you can run it as a cron job, or as a deamon running in the background even when your not loged in on the system. The default running mode is probably the most appreciated, it is running as a normal process, and will be killed when you logout.
It is uptimized for beeing used on a system with alot of users, where the executable will be located for any user to reach. It has a configuration file, that any user can create and costumize for their special purpus. If the default configuration is used, the program will change the .signature file.
OPTIONSThese are the command-line options for sigit:
- -f file <Explicit config file>
- Should you be interrestet in executing sigit with a different configuration file, than the standard ~/.sigitrc or /etc/sigit.rc file, then use this flag to instruct sigit to read your configuration file. Uppon error, Sigit will not try to read any of the standard configuration files.
- -c <cronjob>
- The <cronjob> will be usefull if you decide to run the program as a normal cronjob. This will make sure, the program only creates one signature befor exiting.
- -d <deamonise>
- In order to run the program as a background <deamon> you will have to supply it with the "-d". this change is made, since I found that the most frequent usage might either be as a cron job, or running as a normal process, since you would like it to get killed, once you logout. Hint: "you dont need to change the signatures for your emails, when youre not loged in on the system, since very few people sends emails from their accounts while they're not loged in."
- -h <help>
- Print a nice help screen and exit.
- -v <verbose>
- Sometimes it's good to know how the program is running, and how far it's in the execution. Here comes <verbose> as a very good solution. It will keep all the very specific infos hidden, yet let you know just what part of the program is beeing used, and how it went.
- -vv <very verbose>
- The usage of <very verbose>, is mostly usefull, when you're trying to debug the thing, and you have no idear what caused it to abort. Throw in a couple more v's and see what sort of extra info is displayed :)
- -V <version>
- The -V will print the current version of the program, and exit.
- -H option <Extra help>
- Use the "-H" If you have found an option in the help screen, but dont seem that confident with using it, for a quick refference use this flag to get more describing info on how to use that option.
HINTSIf you use a program, like pine or KMail, that has a few problems reading from fifo's, then provide the nfs_delay setting in the fifo configuration, and it wont matter what program you're using.
When run on multi cluster systems, where your $HOME is mounted as NFS share, and you realy can't control which server the program is started on, it will require rsh(1) to be installed, since this is used in order to kill an allready running process on another server, befor starting the current copy of the program.
License and DisclaimerSigit are Copyright (c) 2000, 2001, 2002, 2003 by Kenneth 'Redhead' Nielsen. Sigit may be used and distributed under the terms of the GNU General Public License. All other brand and product names are trademarks, registered trademarks or service marks of their respective holders.
These programs are 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 distribution; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA.
AcknowledgmentsThanks go to:
AUTHORSigit written by
Kenneth 'Redhead' Nielsen <[email protected]>
Documentation formatting by
Kenneth 'Redhead' Nielsen <[email protected]>
All future infos on the sigit exploration, can be found at: <http://www.redhead.dk>
REPORTING BUGIf you find a bug or problem, please send an email describing the bug to: <[email protected]> with information on:
* A subject containing the word 'Sigit'
* What Sigit version.
* What system you're running.
* What mail/news program you were using when the bug appeared.
* A description on what you tried, when the bug accured.
* A debug/verbose output of the bug. (if one can be made)