|
How can I configure syslogd to log vshelld messages to a separate file?
The following steps describe how to configure vshelld to log its messages to a separate file using the syslog (8) facility.
- Change the vshelld_config (5) option "SyslogFacility" to a unique syslog (8) facility that is not currently used by any other applications on the system. For example, the following line will cause vshelld to log to syslog using the "local3" facility:
SyslogFacility LOG_LOCAL3
- Modify syslog.conf (5) so that messages of the facility you chose in the previous step will be logged to a specific file. For example, the following line will steer any messages to the "local3" facility to the file /var/log/vshelld.
local3.* /var/log/vshelld
Log messages from vshelld will now be appended to /var/log/vshelld.
- Depending on your syslog.conf settings, some or all of your vshelld messages may continue to be appended to other files (such as /var/log/messages). To prevent this, use the "none" syslog level to exclude vshelld messages from being sent to other destinations. For example, including "local3.none" in the following line prevents any vshelld messages (if configured as above) from being appended to /var/log/messages:
# Log anything of level info or higher (except local3).
local3.none;*.info /var/log/messages
For more information on configuring vshelld and syslog, see the vshelld_config (5) and syslog.conf (5) manual pages.
| Three Fast Ways
to Learn More About VShell for Windows and UNIX |
|
|
|
Tell
me more. E-mail us your questions about putting VShell to work for your organization.
|
Try
it today! Download a free 30-day evaluation copy of VShell
for Windows or UNIX.
|
Talk
to us. Let us help define the right VShell server solution
for your company.
|
|
