02.03.2014 Views

Tornado

Tornado

Tornado

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Tornado</strong> 2.0<br />

User’s Guide<br />

actions which cannot be done via windsh (like loading object from a file system local to<br />

the target) have to be performed.<br />

CAVEAT<br />

Redirecting target I/O into the target server’s console may lead side effects:<br />

– If you use -redirectIO when a target shell is running, its I/O will also get redirected<br />

in the target server’s console. You will see a double echo (one echo for the target<br />

server console, and another one by the target shell itself), and the target Shell input<br />

will be lost when the target server stops. Use the -redirectShell in conjunction with -<br />

redirectIO option to avoid this.<br />

– -redirectIO and -redirectShell flags are not exclusives. They can be jointly used. But<br />

in this case, only the target shell will get its input from the target server’s console.<br />

Other tasks pending on a read on their stdin will pend forever (unless the target shell<br />

is destroyed).<br />

– If you use Windsh with a target server which has -redirectIO and -C set, remember<br />

that windsh also redirects the I/O. So if you try<br />

scanf ("%s", buf)<br />

from the command line the input will be done by the windsh, not from the target<br />

server’s console.<br />

– If you use windsh with a target server which has not set -redirectIO and try a<br />

command which launches another task which wants to write messages, you won’t see<br />

them: the child tasks get their I/O reset to the global I/O descriptors (if the target<br />

server was launched with -C, those outputs will be sent in the target server’s console).<br />

Setting -redirectIO without -C will permit to see the task’s child output into the<br />

windsh which launched them. But be aware that ALL TOOLS will be notified of the<br />

target’s task output.<br />

– Using -redirectShell, if the shell cannot be redirected to the target server console, the<br />

characters typed in the console window won’t be echoed, since that the shell’s job to<br />

echo each typed characters.<br />

Target Server File System (TSFS)<br />

Other virtual I/O channels are available for general file I/O. Target tasks can use these<br />

channels to access the host’s file system just as they would access target connected file<br />

systems. This type of virtual I/O is referred to as the Target Server File System or TSFS.<br />

The part of the host’s file system visible to targets using the TSFS is specified with the -R<br />

root option. For example, if a root of “/users/john” is specified, the target will only be<br />

able to access files on the host’s file system within and below /users/john.<br />

By default, the host’s files are accessible for reading only by target processes using the<br />

TSFS. To make the files accessible for reading and writing, -RW should be specified. When<br />

-RW is specified, access to the target server is automatically restricted to host processes<br />

with the same user ID as the target server, as if the -L option was specified.<br />

360

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!