Page 1168
If the file contains passwords, it should not be world-readable.
HISTORY
Written by Rich $alz (rsalz@uunet.uu.net) for InterNetNews.
SEE ALSO
innd(8), newsfeeds(5), nnrpd(8), wildmat(3)
nntpsend.ctl—List of sites to feed via nntpsend.
DESCRIPTION
The file /news/lib/nntpsend.ctl specifies the default list of sites to be fed by nntpsend(8).
Comments begin with a number sign (#) and continue through the end of the line. Blank lines and comments are ignored. All other lines should consist of four fields separated by a colon.
The first field is the name of the site as specified in the newsfeeds(5) file.
The second field should be the hostname or IP address of the remote site.
The third field, if non-empty, specifies the default tail truncation size of site's batchfile. This is passed to shrinkfile as the _s flag. If this field is empty, no truncation is performed.
The fourth field specifies some default flags passed to innxmit(8). The flag _a is always given to innxmit and need not appear here. If no _t timeout flag is given in this field and on the nntpsend command line, _t 180 will be given to innxmit.
HISTORY
Written by Landon Curt Noll (chongo@toad.com) for InterNetNews.
SEE ALSO
innxmit(8), newsfeeds(5), nntpsend(8), trunc(1)
nologin—Prevent usual users from logging into the system.
DESCRIPTION
If the file /etc/nologin exists, login(1) will allow access only to root. Other users will be shown the contents of this file and their logins refused.
FILES
/etc/nologin
SEE ALSO
login(1), shutdown(8)
Linux, 29 December 1992
overview.fmt—Format of news overview database.
Page 1169
DESCRIPTION
The file /news/lib/overview.fmt specifies the organization of the news overview database. Blank lines and lines beginning with a number sign (#) are ignored. The order of lines in this file is important; it determines the order in which the fields will appear in the database.
Most lines will consist of an article header name, optionally followed by a colon. A trailing set of lines can have the word full appear after the colon; this indicates that the header should appear as well as its value.
If this file is changed, it is usually necessary to rebuild the existing overview database using expireover(8) after removing all existing overview files.
The default file, show here, is compatible with Geoff Collyer's nov package:
Subject: From: Date: Message-ID: References: Bytes: Lines: ## Some newsreaders get better performance if Xref is present #Xref:full
HISTORY
Written by Rich $alz (rsalz@uunet.uu.net) for InterNetNews. Intended to be compatible with the nov package written by Geoff Collyer (geoff@world.std.com).
passwd—Password file.
DESCRIPTION
passwd is an ASCII file that contains a list of the system's users and the passwords they must use for access. The password file should have general read permission (many utilities, such as ls(1), use it to map user IDs to usernames) but write access only for the superuser.
In the good old days, there was no great problem with this general read permission. Everybody could read the encrypted passwords, but the hardware was too slow to crack a well-chosen password, and moreover, the basic assumption used to be that of a friendly user community. These days, many people run some version of the shadow password suite, where /etc/passwd has *s instead of passwords, and the encrypted passwords are in /etc/shadow, which is readable by root only.
When you create a new login, leave the password field empty and use passwd(1) to fill it. A star (*) in the password field means that this user cannot log in via login(1).
There is one entry per line, and each line has the format:
login_name:passwd:UID:GID:user_name:directory:shell
The field descriptions are
| login_name | The name of the user on the system. |
| password | The encrypted optional user password. |
| UID | The numerical user ID. |
| GID | The numerical group ID for this user. |
| user_name | The (optional) comment field (often a full username). |
| directory | The user's $HOME directory. |
| shell | The program to run at login (if empty, use /bin/sh). |
Page 1170
NOTE
If your root file system is on /dev/ram, you must save a changed password file to your root filesystem floppy before you shut down the system and check the access rights. If you want to create user groups, their GIDs must be equal and there must be an entry in /etc/group, or no group will exist.
FILES
/etc/passwd
SEE ALSO
passwd(1), login(1), group(5), shadow(5)
Linux, 24 July 1993
passwd.nntp—Passwords for connecting to remote NNTP servers.
DESCRIPTION
The file /news/lib/passwd.nntp contains host-name-password triplets for use when authenticating client programs to NNTP servers. This file is normally interpreted by the NNTPsend-password routine in libinn(3). Blank lines and lines beginning with a number sign (#) are ignored. All other lines should consist of three or fields separated by colons:
host:name:password host:name:password:style
The first field is the name of a host and is matched in a case-insensitive manner. The second field is a username, and the third is a password. The optional fourth field specifies the type of authentication to use. The default is authinfo, which means that NNTP authinfo commands are used to authenticate to the remote host. If either the username or password are empty, then the related command will not be sent. (The authinfo command is a common extension to RFC 977.) For example:
## UUNET needs a password, MIT doesn't. mit.edu:bbn::authinfo uunet.uu.net:bbn:yoyoma:authinfo
This file should not be world-readable.
HISTORY
Written by Rich $alz (rsalz@uunet.uu.net) for InterNetNews.
SEE ALSO
innd(8), libinn(3)
pbm—Portable bitmap file format.
DESCRIPTION
The portable bitmap format is a lowest common denominator monochrome file format. It was originally designed to make it reasonable to mail bitmaps between different types of machines using the typical stupid network mailers we have today. Now it serves as the common language of a large family of bitmap conversion filters. The definition is as follows:
A "magic number" for identifying the file type. A pbm file's magic number is the two characters P1.
Page 1171
Whitespace (blanks, Tabs, CRs, LFs).
A width, formatted as ASCII characters in decimal.
Whitespace.
A height, again in ASCII decimal.
Whitespace.
Width * height bits, each either 1 or 0, starting at the top-left corner of the bitmap, proceeding in normal English reading order.
The character 1 means black; 0 means white.
Whitespace in the bits section is ignored.
Characters from a # to the next end-of-line are ignored (comments).
No line should be longer than 70 characters.
Here is an example of a small bitmap in this format:
P1 # feep.pbm 24 7 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 0 0 1 1 1 1 0 0 1 1 1 1 0 0 1 1 1 1 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 1 0 0 1 1 1 0 0 0 1 1 1 0 0 0 1 1 1 0 0 0 1 1 1 1 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 1 1 1 1 0 0 1 1 1 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Programs that read this format should be as lenient as possible, accepting anything that looks remotely like a bitmap.
There is also a variant on the format, available by setting the RAWBITS option at compile time. This variant is different in the following ways:
The "magic number" is P4 instead of P1.
The bits are stored eight per byte, high bit first and low bit last.
No whitespace is allowed in the bits section, and only a single character of whitespace (typically a newline) is allowed after the height.
The files are eight times smaller and many times faster to read and write.
SEE ALSO
atktopbm(1), brushtopbm(1), cmuwmtopbm(1), g3topbm(1), gemtopbm(1), icontopbm(1), macptopbm(1), mgrtopbm(1), pi3topbm(1), xbmtopbm(1), ybmtopbm(1), pbmto10x(1), pnmtoascii(1), pbmtoatk(1), pbmtobbnbg(1), pbmtocmuwm(1), pbmtoepson(1), pbmtog3(1), pbmtogem(1), pbmtogo(1), pbmtoicon(1), pbmtolj(1), pbmtomacp(1), pbmtomgr(1), pbmtopi3(1), pbmtoplot(1), pbmtoptx(1), pbmtox10bm(1), pbmtoxbm(1), pbmtoybm(1), pbmtozinc(1), pbmlife(1), pbmmake(1), pbmmask(1), pbmreduce(1), pbmtext(1), pbmupc(1), pnm(5), pgm(5), ppm(5)
AUTHOR
Copyright 1989, 1991 by Jef Poskanzer.
27 September 1991
pgm—Portable graymap file format.