Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

crashmail(1) [debian man page]

CRASHMAIL(1)							     CrashMail							      CRASHMAIL(1)

NAME
crashmail - A Fidonet *.JAM and MSG tosser SYNOPSIS
crashmail [SETTINGS filename] [SCAN] [TOSS] [TOSSFILE filename] [TOSSDIR directory] [SCANAREA area] [SCANLIST filename] [RESCAN area RES- CANNODE node [RESCANMAX max]] [VERSION] [LOCK] [UNLOCK] [NOSECURITY] DESCRIPTION
Welcome to CrashMail II! CrashMail II is basically a more portable version of CrashMail, my tosser for Amiga computers. Users of the old Amiga version will probably find some things familiar while some features are gone such as the ARexx port (for obvious reasons!) and the GUI configuration editor. The only feature that CrashMail II has and the old CrashMail hasn't is support for JAM messagebases. OPTIONS
SCAN Scan all areas for messages to export. TOSS Toss all .pkt files and bundles in inbound directory. TOSSFILE filename Toss the specified file. TOSSDIR directory Toss all files in the specified directory. SCANAREA area Scan the specified area. SCANLIST filename Scan all areas listed in the specified file. RESCAN area RESCANNODE node RESCANMAX max Rescans the specied area for the specied node. If RESCANMAX is specified, it sets the maximum number of messages to rescan. SETTINGS filename Use this configuration file instead of the default.You can use the environment variable CMCONFIGFILE to set the default configura- tion file. VERSION Show version information about CrashMail. LOCK Locks CrashMail's configuration file and then exits. CrashMail has a simple locking mechanism to ensure that two instances of Crash- Mail never use the same configuration file at the same time. You can use this if you want to temporarily want to stop CrashMail from running, e.g. when updating the nodelist. UNLOCK Removes the lock on CrashMail's configuration file. Only use this when the configuration file previously has been locked with LOCK, otherwise terrible things might happen. NOSECURITY Process all packets without security checks. This is intended to be used mainly with TOSSDIR/TOSSFILE and with packets created by CrashWrite. SEE ALSO
crashexport(1), crashlist(1), crashmaint(1), crashwrite(1), crashgetnode(1), crashstats(1) FILES
crashmail.prefs BUGS
Win32 If you want to use an old reader that only can handle 8+3 filenames, you have to use %8 in the path of your DEFAULT area if you are using the auto-add feature. This creates an 8 digit serial number to use as the path for the area. Note that if CrashMail is run twice in a short period of time (a few seconds), it might create duplicate paths. Avoid %8 if it is at all possible. Linux Don't use the ~ character in paths. Such paths are expanded to point to your home directory by the shell and not by the i/o functions in the system. They will not work in CrashMail. In *.msg areas, make sure that all files are named *.msg and not *.MSG! If they are not named in lowercase, CrashMail will not export them. As an extra bonus, the Linux version of CrashMail can use the syslog instead of using its own log file. Just use "syslog" as the name of your log file. If the precompiled binaries in the CrashMail archive don't work on your system, you will have to compile your own. See src/ReadMe.txt for more information about this. AUTHOR
CrashMail is written by Johan Billing <billing@df.lth.se> This manual page was written by Peter Karlsson <peter@softwolves.pp.se> Johan Billing 1999-08-01 CRASHMAIL(1)

Check Out this Related Man Page

tpm_nvread(8)															     tpm_nvread(8)

NAME
tpm_nvread SYNOPSIS
tpm_nvread [OPTIONS] DESCRIPTION
tpm_nvread reads data from an NVRAM area and either displays them or writes them into a file. The user must provide the index of the NVRAM area. If the user provided the number of bytes to read then this will be the maximum number of bytes that will be read from the NVRAM area, otherwise the whole NVRAM area will be read. Some NVRAM areas only allow read sizes of zero, i.e., NVRAM area with index 0. Optionally an offset into the NVRAM area can be given where the reading of the data is to start. If the NVRAM area has permission bits set that require owner or NVRAM area authentication, then the password must be provided via the password option. The following options are supported: -h, --help Display command usage info. -v, --version Display command version info. -l, --log [none|error|info|debug] Set logging level. -u, --unicode Use TSS UNICODE encoding for passwords to comply with applications using TSS popup boxes -z, --well-known Use a secret of all zeros (20 bytes of zeros) as either the NVRAM area or owner secret. -p, --password Depending on what type of authentication is required for the NVRAM area, this must either be the NVRAM area or owner password. A password may be directly provided for example by using '--password=password' or '-ppassword'. If no password is provided then the program will prompt the user for the password. -i, --index The index of the NVRAM area. The parameter may either be a decimal number or a hexadecimal number starting with '0x'. -s, --size The number of bytes to read from the NVRAM area. The parameter may either be a decimal number or a hexadecimal number starting with '0x'. -n, --offset (optional parameter) The offset into the NVRAM area from where to start reading. The parameter may either be a decimal number or a hexadecimal number starting with '0x'. -f, --filename (optional parameter) The name of a file the read data will be written into. If no filename is given the data will be printed to stdout. SEE ALSO
tpm_nvdefine(8), tpm_nvinfo(8), tpm_nvrelease(8), tpm_nvwrite(8) REPORTING BUGS
Report bugs to <trousers-users@lists.sourceforge.net> TPM Management 2011-07-11 tpm_nvread(8)
Man Page