|
|
1.1 ! root 1: .TH CHFN 1 "17 March 1982 deprecated" ! 2: .UC 4 ! 3: .SH NAME ! 4: chfn \- change finger entry ! 5: .SH SYNOPSIS ! 6: .B chfn ! 7: [loginname] ! 8: .SH DESCRIPTION ! 9: .I Chfn ! 10: is used to change information about users. This information is used ! 11: by the finger program, among others. ! 12: It consists of the user's ! 13: "real life" name, office number, office phone number, and home ! 14: phone number. ! 15: .I Chfn ! 16: prompts the user for each field. ! 17: Included in the prompt is a default value, ! 18: which is enclosed between brackets. ! 19: The default value is accepted simply by typing <return>. ! 20: To enter a blank field, ! 21: type the word 'none'. ! 22: Below is a sample run: ! 23: .IP ! 24: .B "Name [Biff Studsworth II]:" ! 25: .br ! 26: .B "Office number (Exs: 597E or 197C) []:" ! 27: 521E ! 28: .br ! 29: .B "Office Phone (Ex: 1632) []:" ! 30: 1863 ! 31: .br ! 32: .B "Home Phone (Ex: 987532) [5771546]:" ! 33: none ! 34: .sp ! 35: .PP ! 36: .I Chfn ! 37: allows phone numbers to be entered with or without hyphens. ! 38: .PP ! 39: It is a good idea to run finger after running ! 40: .I chfn ! 41: to make sure everything is the way you want it. ! 42: .PP ! 43: The optional argument ! 44: .B loginname ! 45: is used to change another person's finger information. ! 46: This can only be done by the super-user. ! 47: .SH FILES ! 48: /etc/passwd, /etc/ptmp ! 49: .SH SEE\ ALSO ! 50: finger(1), passwd(5) ! 51: .SH BUGS ! 52: For historical reasons, the user's name, etc are stored in the passwd file. ! 53: This is a bad place to store the information. ! 54: Rumors are that a data base is being developed to store this information, ! 55: but don't hold your breath. ! 56: .PP ! 57: Because two users may try to write the passwd file at once, a synchronization ! 58: method was developed. ! 59: On rare occasions, a message that the password file ! 60: is "busy" will be printed. ! 61: In this case, ! 62: .I chfn ! 63: sleeps for a while and then tries to write to the passwd file again.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.