|
DataMuseum.dkPresents historical artifacts from the history of: DKUUG/EUUG Conference tapes |
This is an automatic "excavation" of a thematic subset of
See our Wiki for more about DKUUG/EUUG Conference tapes Excavated with: AutoArchaeologist - Free & Open Source Software. |
top - metrics - downloadIndex: T n
Length: 1582 (0x62e) Types: TextFile Names: »ntail.1«
└─⟦2d1937cfd⟧ Bits:30007241 EUUGD22: P.P 5.0 └─⟦dc59850a2⟧ »EurOpenD22/pp5.0/pp-5.tar.Z« └─⟦e5a54fb17⟧ └─⟦this⟧ »pp-5.0/man/man1/ntail.1«
.TH NTAIL 1L .\" @(#) $Header: /cs/research/pp/hubris/pp-beta/man/man1/RCS/ntail.1,v 5.0 90/09/20 16:52:51 pp Exp Locker: pp $ .\" .\" $Log: ntail.1,v $ .\" Revision 5.0 90/09/20 16:52:51 pp .\" rcsforce : 5.0 public release .\" .\" .SH NAME ntaiL - Watch the growth of files. .SH SYNTAX .B ntail entry ... .SH DESCRIPTION .I Ntail monitors one or more files, and displays all data written to a file since command invocation. It is very useful for monitoring multiple logfiles simultaneously. .P If an .I entry given on the command line is a directory, all files in that directory will be monitored, including those created after the .I ntail invocation. If an .I entry given on the command line doesn't exist, .I ntail will watch for it and monitor it once created. When switching files in the display, a banner showing the pathname of the file is printed. .P An interrupt character (usually CTRL/C or DEL) will display a list of the most recently modified files being watched. Send a quit signal (usually CTRL/backslash) to stop .IR ntail . .SH SEE ALSO tail(1) .SH NOTES .I Ntail may be easily confused. For example, if a file is renamed, .I ntail may or may not continue to monitor it. If you ask it to monitor a file multiple times, it probably will. If you misspell a filename, .I ntail will treat it as a nonexistent entry and happily wait for its creation. .P My favorite use is "ntail /usr/spool/uucp/.Log/*". .br Ntail was originally called xtail, and was changed for reasons you don't want to know about... .SH AUTHOR Chip Rosenthal <chip@vector.Dallas.TX.US>