Be sure to escape any special characters in the message ID from the shell. Single quotes are recommended for this purpose since many message IDs contain dollar signs.

-e

Only print the storage token if the article is stored on the system. (In other words, suppress the "/dev/null" or "not found" output for missing or remembered articles.)

-f db

Query the history database db rather than the default history database.

-i

Rather than expecting a message ID on the command line, grephistory will read a list of message IDs on standard input, one per line. Leading and trailing whitespace is ignored, as are any malformed lines. It will print out standard output those message IDs which are not found in the history database. This is used when processing "ihave" control messages.

-l

Display the entire line from the history database, rather than just the storage API token.

-n

If the message ID is present in the history database but has no storage API token, print "/dev/null" and exit successfully. This can happen if an article has been cancelled or expired, but history information has still been retained. This is the default behavior.

-q

Don't print any message, but still exit with the appropriate status.

-s

Rather than expecting a message ID on the command line, grephistory will read a list of message IDs on standard input, one per line. Leading and trailing whitespace is ignored, as are any malformed lines. It will print on standard output the storage API tokens for any articles that are still available, one per line. This flag is used when processing "sendme" control messages.

-v

Print out the hash of the message ID for diagnostic purposes, as well as any other requested information. This flag is not useful with -s.

$Id: grephistory.1 7045 2004-12-19 19:37:45Z rra $