06.05.2013 Views

The eG Installation Guide - eG Innovations

The eG Installation Guide - eG Innovations

The eG Installation Guide - eG Innovations

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Installing and Configuring on Unix<br />

6. Finally, save the start_agent script.<br />

7. Restart the agent.<br />

Figure 2.20: <strong>The</strong> edited start_agent script<br />

In Solaris environments, error and output logging for the <strong>eG</strong> agent can be triggered by editing the<br />

starta script in the /opt/egurkha/bin directory. <strong>The</strong> steps involved in this process are discussed hereunder:<br />

1. Open the starta file.<br />

2. Edit the line that begins with nohup java –client -Xrs . . . (see Figure 2.21).<br />

Figure 2.21: <strong>The</strong> starta script<br />

3. At the end of the line indicated by Figure 2.21, you can find an entry that reads as follows: . . .<br />

/dev/null 2>&1.<br />

4. This entry is appended to the nohup java line by default, and indicates that both output and error<br />

logging is not enabled for the <strong>eG</strong> agent in question, by default.<br />

5. Unlike Linux, HPUX, and AIX agents, which can be configured with two separate log files for error<br />

and output logging respectively, the agent on Solaris can only be configured with a single log file;<br />

both errors and output will be captured by this log file only. <strong>The</strong>refore, to enable error and output<br />

logging, replace the /dev/null entry in the nohup line with the full path to the log file (see Figure<br />

Figure 2.22).<br />

69

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

Saved successfully!

Ooh no, something went wrong!