MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
41 bytes removed ,  2 March 2023
no edit summary
No edit summary
No edit summary
Line 64: Line 64:
     is derived from  <b>zsh</b> and is the shell variant which is set in /etc/shells for MCP. In an authenticated session, the launch link normally results is a WebSSH session with this shell. Aside from the modification for the MCP machine model, it is otherwise just zsh however the following commands are available to establish different shell behaviour in support of the KEE:
     is derived from  <b>zsh</b> and is the shell variant which is set in /etc/shells for MCP. In an authenticated session, the launch link normally results is a WebSSH session with this shell. Aside from the modification for the MCP machine model, it is otherwise just zsh however the following commands are available to establish different shell behaviour in support of the KEE:
<ul><li><b>shcl</b> (common lisp nature)</li><li><b>shhs</b> (HsShellScript, haskell nature)</li><li><b>upsh</b> (prolog nature)</li></ul>
<ul><li><b>shcl</b> (common lisp nature)</li><li><b>shhs</b> (HsShellScript, haskell nature)</li><li><b>upsh</b> (prolog nature)</li></ul>
   <b>mcpcms</b> can be accessed with ssh using the following script
   <b>mcpcms</b> can be accessed with ssh using the following script<pre><tt>#!/usr/bin/bash
    <pre><tt>
#!/usr/bin/bash
#
#
# invoke this script with <fileName> &lt;req-spec&gt;
# invoke this script with &lt;fileName&gt; &lt;connect-spec&gt;
 
# where             
                where             
#       
         
&lt;connect-spec&gt;::= ipV6Address:port | ipV4Address:port | FQDSAgentName  
                &lt;req-spec&gt;   ::= ipV6Address:port | ipV4Address:port | FQDSAgentName  
FQDSAgentName ::= &lt;agentId&gt;@&lt;domain&gt;[:&lt;port&gt;]
                FQDSAgentName ::= &lt;agentId&gt;@&lt;domain&gt;[:&lt;port&gt;]
#
 
and the port is displayed in the device control block of your DCMS account profile. Using the FQDSAgentName is equivalent to what the launch does.
                and the port is displayed in a DS control block in the user's DCMS account profile or provided dynamically by automation in an authe
ssh
ssh
    </tt></pre>  
</tt></pre>  
   </blockquote>
   </blockquote>
   <b>WFL</b>
   <b>WFL</b>

Navigation menu