grephistory man page on YellowDog

Man page or keyword search:  
man Server   18644 pages
apropos Keyword Search (all sections)
Output format
YellowDog logo
[printable version]

GREPHISTORY(1)		  InterNetNews Documentation		GREPHISTORY(1)

NAME
       grephistory - Query the INN history database

SYNOPSIS
       grephistory [-eilnqsv] [-f db] [message-id]

DESCRIPTION
       grephistory queries the INN history database for information about the
       specified message ID.  If no flags are given, the program prints the
       storage API token of the corresponding article, or "/dev/null" if the
       article is listed in the history database but not stored on the server.
       If the message ID cannot be found in the database, grephistory will
       print "grephistory: not found" and exit with a non-zero status.

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

OPTIONS
       -e  Only print the storage token if the article is stored on the sys‐
	   tem.	 (In other words, suppress the "/dev/null" or "not found" out‐
	   put for missing or remembered articles.)

       -f db
	   Query the history database db rather than the default history data‐
	   base.

       -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 process‐
	   ing "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 sta‐
	   tus.

       -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.

HISTORY
       Written by Rich $alz <rsalz@uunet.uu.net> for InterNetNews.  Rewritten
       in POD by Russ Allbery <rra@stanford.edu>.

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

SEE ALSO
       history(5), inn.conf(5)

INN 2.4.2			  2004-12-19			GREPHISTORY(1)
[top]

List of man pages available for YellowDog

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net