o5r/plan9port
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

checkpoint

Browse source
This commit is contained in:
rsc 2005-01-14 03:45:44 +00:00
parent 2634795b5f
commit 78e51a8c66
314 changed files with 48199 additions and 300 deletions
Download patch file Download diff file Expand all files Collapse all files

79
man/man4/9pserve.html Normal file
View file

@ -0,0 +1,79 @@
<head>
<title>9pserve(4) - Plan 9 from User Space</title>
<meta content="text/html; charset=utf-8" http-equiv=Content-Type>
</head>
<body bgcolor=#ffffff>
<table border=0 cellpadding=0 cellspacing=0 width=100%>
<tr height=10><td>
<tr><td width=20><td>
<tr><td width=20><td><b>9PSERVE(4)</b><td align=right><b>9PSERVE(4)</b>
<tr><td width=20><td colspan=2>
<br>
<p><font size=+1><b>NAME </b></font><br>
<table border=0 cellpadding=0 cellspacing=0><tr height=2><td><tr><td width=20><td>
9pserve &ndash; announce and multiplex 9P service<br>
</table>
<p><font size=+1><b>SYNOPSIS </b></font><br>
<table border=0 cellpadding=0 cellspacing=0><tr height=2><td><tr><td width=20><td>
<tt><font size=+1>9pserve</font></tt> [ <tt><font size=+1>&#8722;v</font></tt> ] <i>addr<br>
</i>
</table>
<p><font size=+1><b>DESCRIPTION </b></font><br>
<table border=0 cellpadding=0 cellspacing=0><tr height=2><td><tr><td width=20><td>
On Plan 9, when a user-level file server mounts itself into a
name space or posts itself in <tt><font size=+1>/srv</font></tt>, the Plan 9 kernel multiplexes
the potentially many processes accessing the server into a single
9P conversation. The user-level server need not concern itself
with how many processes are accessing it or with cleaning up
after a process when it exits unexpectedly. On Unix, <i>9pserve</i> takes
the place of the Plan 9 kernel, multiplexing clients onto a single
server conversation and cleaning up after clients when they hang
up unexpectedly.
<table border=0 cellpadding=0 cellspacing=0><tr height=5><td></table>
<i>9pserve</i> announces a 9P service on <i>addr</i> and multiplexes any 9P
clients connecting to <i>addr</i> into a single conversation with a 9P
server on <i>9pserve</i>&#8217;s standard input and output. When a client hangs
up, <i>9pserve</i> flushes any outstanding 9P transactions and clunks
any outstanding fids belonging to the client.
<table border=0 cellpadding=0 cellspacing=0><tr height=5><td></table>
<i>9pserve</i> is typically not invoked directly; use <a href="../man3/post9pservice.html"><i>post9pservice</i>(3)</a>
instead.<br>
</table>
<p><font size=+1><b>SEE ALSO </b></font><br>
<table border=0 cellpadding=0 cellspacing=0><tr height=2><td><tr><td width=20><td>
<a href="../man4/intro.html"><i>intro</i>(4)</a>, <i>intro</i>(9p)<br>
</table>
<p><font size=+1><b>SOURCE </b></font><br>
<table border=0 cellpadding=0 cellspacing=0><tr height=2><td><tr><td width=20><td>
<tt><font size=+1>/usr/local/plan9/src/cmd/9pserve.c<br>
</font></tt>
</table>
<td width=20>
<tr height=20><td>
</table>
<!-- TRAILER -->
<table border=0 cellpadding=0 cellspacing=0 width=100%>
<tr height=15><td width=10><td><td width=10>
<tr><td><td>
<center>
<a href="../../"><img src="../../dist/spaceglenda100.png" alt="Space Glenda" border=1></a>
</center>
</table>
<!-- TRAILER -->
</body></html>