Query: cpu
OS: plan9
Section: 1
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
CPU(1) General Commands Manual CPU(1)NAMEcpu - connection to cpu serverSYNOPSIScpu [ -h server ] [ -c cmd args ... ]DESCRIPTIONCpu starts an rc(1) running on the server machine, or the machine named in the $cpu environment variable if there is no -h option. Rc's standard input, output, and error files will be /dev/cons in the name space where the cpu command was invoked. Normally, cpu is run in an 81/2(1) window on a terminal, so rc output goes to that window, and input comes from the keyboard when that window is current. Rc's cur- rent directory is the working directory of the cpu command itself. The name space for the new rc is an analogue of the name space where the cpu command was invoked: it is the same except for architecture- dependent bindings such as /bin and the use of fast paths to file servers, if available. If a -c argument is present, the remainder of the command line is executed by rc on the server, and then cpu exits. The name space is built by running /usr/$user/lib/profile with the root of the invoking name space bound to /mnt/term. The service envi- ronment variable is set to cpu; the cputype and objtype environment variables reflect the server's architecture.FILESThe name space of the terminal side of the cpu command is mounted on the CPU side on directory /mnt/term.SOURCE/sys/src/cmd/cpu.cSEE ALSOrc(1), 81/2(1)BUGSBinds and mounts done after the terminal lib/profile is run are not reflected in the new name space. CPU(1)
Related Man Pages |
---|
drawterm(1) - debian |
cpu(1) - plan9 |
cpuset(3) - netbsd |
cpuset_destroy(3) - netbsd |
cpuset_size(3) - netbsd |
Similar Topics in the Unix Linux Community |
---|
Load average in squeeze too low |
grep hogs entire cpu |
Sending sms from UNIX server |
How many cpu on t5-2? |
Wine cause more cpu usage and freeze program for a couple of seconds |