1 .TH 9PSERVE 4
2 .SH NAME
3 9pserve \- announce and multiplex 9P service
4 .SH SYNOPSIS
5 .B 9pserve
6 [
7 .B -lv
8 ]
9 [
10 .B -A
11 .I aname
12 .I afid
13 ]
14 [
15 .B -M
16 .I msize
17 ]
18 .I addr
19 .SH DESCRIPTION
20 On Plan 9, when a user-level file server mounts itself into a name space
21 or posts itself in 
22 .BR /srv ,
23 the Plan 9 kernel multiplexes the potentially many processes 
24 accessing the server into a single 9P conversation.
25 The user-level server need not concern itself with how many
26 processes are accessing it or with cleaning up after a process when it
27 exits unexpectedly.
28 On Unix,
29 .I 9pserve
30 takes the place of the Plan 9 kernel, multiplexing clients onto
31 a single server conversation and cleaning up after clients when
32 they hang up unexpectedly.
33 .PP
34 .I 9pserve
35 announces a 9P service on
36 .I addr
37 and multiplexes any 9P clients connecting to
38 .I addr
39 into a single conversation with a 9P server on
40 .IR 9pserve 's
41 standard input and output.
42 When a client hangs up, 
43 .I 9pserve
44 flushes any outstanding 9P transactions 
45 and clunks any outstanding fids belonging to the client.
46 .PP
47 .I 9pserve
48 is typically not invoked directly; use
49 .IR post9pservice (3)
50 instead.
51 .PP
52 The options are:
53 .TP
54 .B -l
55 logging; write a debugging log to
56 .IB addr .log \fR.
57 .TP
58 .B -v
59 verbose; more verbose when repeated
60 .TP
61 .B -A
62 rewrite all attach messages to use
63 .I aname
64 and
65 .IR afid ;
66 used to implement
67 .IR srv (4)'s
68 .B -a
69 option
70 .TP
71 .B -M
72 do not initialize the connection with a
73 .B Tversion
74 message;
75 instead assume 9P2000 and a maximum message size of
76 .IR msize
77 .PD
78 .SH "SEE ALSO
79 .IR intro (4),
80 .IR intro (9p)
81 .SH SOURCE
82 .B \*9/src/cmd/9pserve.c