25.06.2015 Views

Administering Platform LSF - SAS

Administering Platform LSF - SAS

Administering Platform LSF - SAS

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Differences from Other Shells<br />

Differences from Other Shells<br />

@ character<br />

When a command is running in the foreground on a remote host, all keyboard<br />

input (type-ahead) is sent to the remote host. If the remote command does not<br />

read the input, it is lost.<br />

lstcsh has no way of knowing whether the remote command reads its<br />

standard input. The only way to provide any input to the command is to send<br />

everything available on the standard input to the remote command in case the<br />

remote command needs it. As a result, any type-ahead entered while a remote<br />

command is running in the foreground, and not read by the remote command,<br />

is lost.<br />

The @ character has a special meaning when it is preceded by white space. This<br />

means that the @ must be escaped with a backslash \ to run commands with<br />

arguments that start with @, like finger. This is an example of using finger<br />

to get a list of users on another host:<br />

% finger @other.domain<br />

Normally the finger command attempts to contact the named host. Under<br />

lstcsh, the @ character is interpreted as a request for remote execution, so the<br />

shell tries to contact the RES on the host other.domain to remotely execute<br />

the finger command. If this host is not in your <strong>LSF</strong> cluster, the command fails.<br />

When the @ character is escaped, it is passed to finger unchanged and<br />

finger behaves as expected.<br />

% finger \@hostB<br />

For more details on the @ character, see “@ character” on page 556.<br />

552<br />

<strong>Administering</strong> <strong>Platform</strong> <strong>LSF</strong>

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

Saved successfully!

Ooh no, something went wrong!