|
|
| − | <CODE>'exec'</CODE> will fork off the specified command and return the exit status | + | <CODE>'exec'</CODE> will run the specified command and return the exit status |
| − | and/or the output. Arguments are passed directly to the command. | + | and output. Any arguments are passed directly to the command, with no special interpretation. |
| | | | |
| | <CODE>'sh'</CODE> is similar, but invokes a shell to run the command line given. | | <CODE>'sh'</CODE> is similar, but invokes a shell to run the command line given. |
| | This means that quoted arguments will be recognised as such, and also | | This means that quoted arguments will be recognised as such, and also |
| − | allows redirection, and other similar shell interpretation. | + | allows redirection, and other similar shell interpretation. The results |
| | + | are returned in exactly the same way. |
| | | | |
| − | Neither of these mechanisms require the command to have any
| + | <CODE>'extend'</CODE> is also similar, but provides a richer and more |
| − | knowledge of the fact that they are being used in this manner. | + | flexible MIB framework - both for configuring the exact command to be |
| | + | run, and for displaying the results. |
| | + | |
| | + | None of these mechanisms require the command to have any |
| | + | knowledge of SNMP, or the fact that they are being used in this manner. |
| | But the output is returned in a fixed format, and it is up to | | But the output is returned in a fixed format, and it is up to |
| | the receiving application to interpret this appropriately. | | the receiving application to interpret this appropriately. |
| | | | |
Exception encountered, of type "Error"