Hi all
I have tried to set syslog settings with instructions from http://kb.vmware.com/kb/1016621 But it looks like that I made something wrong or instructions are not correct.
I use VMware ESXi 4.1.0 build-260247 server.
syslogd service from this host reports that "Note that this version of syslogd ignores /etc/syslog.conf." BUT if I use vSphere client to set syslog local log path, it stores my changes in "/etc/syslog.conf" and these settings work after host restart. Manual changes of this file work also.
Furthermore, any changes in "/etc/vmware/init/init.d/07.logger" file (kb recommended way) are ignored and this file is reverted to its original state after host restart.
Can anybody clarify this behavior? Thanks!
Modifying through the client would be the preferred method, as the manual edit method, as the kb states, may not be retained after restart or not run properly on some systems.
-KjB
Thanks for answer. I saw this note about "some cases" but decided to clarify.
well, then can I use "7.loggger" to set rotate settings? Or it doesn't supported also.
The setting should work, but the problem still remains that in some cases, your changes may not be retained. I don't really like reading notes like that personally, but it is there for a reason. So, the safe bet is to use the GUI, where the note does not apply, but in most cases, modifying that file "should" work just fine.
-KjB
ok, got it. Thanks
I do think the KB article is incorrect. The 07.logger init entry is intended for the early startup of the logger when things like datastores might not be mounted yet. The original intent of the KB article may heve been to address some other issue and somehow morphed into something else. I will bring it to the attention of the KB team.
Thanks, it would be nice! Actually comments in the "7.logger" forward us to the "94.syslogd" file where we can find that syslogd works with "/etc/syslog.conf" file and "logfile=" setting is used as a log file path.