----- Original Message -----
On Tue, Jul 16, 2013 at 08:58:40PM -0400, Ding Yi Chen wrote:
You still have not addressed the third party programs and scripts that monitor /var/log/messages
A) If someone is installing a program that expects this file, they can also install rsyslog.
a) From what command they know they need to install rsyslog if they want yum -y whatprovides /var/log/messages gives no result. If I did not follow the fedora-devel, I would not know why the scripts failed.
b) For user that do upgrade from backup user data/scripts->fresh install->restore data/scrips How they suppose to know that /var/log/messages is gone without checking the Release-Notes? Not everyone have time to go through all the changes.
c) why add the complexity on the script when you don't have to?
B) Fedora, RHEL, and most Red Hat derived distributions use /var/log/messages, but not all do -- for example, Rocks (common in HPC) breaks out syslog messages into individual files per facility. Debian and Ubuntu? Totally diferent. (/var/log/syslog)
So, these third-party scripts need to be flexible anyway. I don't think this is a very strong point in the conversation.
You falsely assume that: a) 3rd party developers support every operating systems under the sun, including all version of Windows, DOS and MacOS. b) 3rd party developers aware the changes c) 3rd party developers can and will diligently update their script just for Fedora.
Don't tell me that you have not seen people writing multiple platform scripts like this:
case $OS) Windows* ) some_windows_scripts ...... Linux* ) grep /var/log/messages .....
For them: What? Fedora 20 does not work while Fedora 19 does? Blame Fedora then.
And for fedora specific 3rd party scripts, now they need to add additional check logic on their script. Sometime that's just too much to ask.
-- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ mattdm@fedoraproject.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel