I get Greg/Michael's point. What is frustrating to me about the conf file overwriting I often see a conf file written appended with .rpmnew if an existing conf file is being respected or the old one being moved to .rpmold if a conf file is replacing the older. The latter case is particularly important to me since just overwriting conf files without saving a backup of the one being overwritten is way beyond rude.
If Centos/SL rpms for sendmail just overwrite the sendmail.mc well, I'm just amazed. So much of the redhat derived rpms honor the .rpmnew/.rpmold method I'm fairly amazed that sendmail would not. > -----Original Message----- > From: Roy Urick [mailto:[email protected]] > Sent: Friday, April 06, 2012 9:34 AM > To: 'BlueOnyx General Mailing List' > Subject: [BlueOnyx:10068] Re: Conf files replaced by update > > Fair enough. I have an easy fix after doing the changes by hand > repeatedly; Once I notice it I have it fixed in about 60 seconds. > > I'll probably start monitoring the file for changes using my > Solarwinds server to get a little more visibility and fix it as soon > as it happens not when I notice mail failing. > > Thanks for the insight. > > > -----Original Message----- > From: [email protected] [mailto:blueonyx- > [email protected]] On Behalf Of Greg Kuhnert > Sent: Friday, April 06, 2012 8:58 AM > To: [email protected] > Subject: [BlueOnyx:10067] Re: Conf files replaced by update > > Hi Roy. > > On 4/6/2012 9:25 PM, Roy Urick wrote: > > I'm with Frank. I too can confirm the .mc file gets overwritten > for seemingly no good reason. I have several tweaks in my file that > when replaced causes mail to stop flowing In my environment. It's > quite frustrating to one day discover my mail server is "broken" and > I have to go in and re-apply my config file changes. > > I have not had a specific chat to Michael to discuss this, but let me > give a generic answer. Type this command on your console. > > rpm -qif /etc/mail/sendmail.mc > > When you type that command, you will notice it was built at > builder10.centos.org for 5106R (and I assume an SL buildhost for > 5107/5108). > > The sendmail.mc file in this case is not owned by a BlueOnyx > generated RPM. I have not specifically investigated this specific > issue... but at face value - the file is dependent on upstream RPM > files. Sometimes, problems in the way the upstream files are created > can cause problems. > > We could make our own SPEC files for each and every RPM in BlueOnyx, > but it would be impossible to manage. > > I hope that helps to understand that sometimes, conf file overwrites > are not something that can be controlled by this project. > > Regards, > Greg. > > > On Apr 6, 2012, at 3:39 AM, Frank Soyer<[email protected]> wrote: > > > >> Hi again, > >> > >> Le 04/04/2012 16:17, Michael Stauber a écrit : > >>>>> Generally you shouldn't modify your sendmail.cf. Any > modification > >>>>> should go into sendmail.mc, which our updates will never > >>>>> overwrite. So whenever sendmail.cf is rebuilt from the > sendmail.mc > >>>>> during an update, your changes will be retained. > >>>> Are you sure ? When I modify the .cf, I need to compile the .mc > >>>> file as sendmail only know this one. > >>> Yes, I am sure. The sendmail.cf is compiled from the sendmail.mc, > so > >>> your changes ought to go into sendmail.mc > >> Sorry to come back to this issue. I was busy last days but I've > >> recheck my configuration this morning : in fact I was not upside > >> down... It's the sendmail.mc file that I modified, not the .cf, > then > >> compiled sendmail.cf. So it's really the .mc file, modified, that > is > >> overwritten by the updates. > >> > >> If you confirm that this is not a right way for yum to do the > >> updates, what can be the reason for it to overwrite this file ? I > >> think that if this file is overwritten, no reason for others > >> configuration files to be overwritten. And there is always some > tweaks on a server ! > >> > >> Thanks. > >> Frank > >> _______________________________________________ > >> Blueonyx mailing list > >> [email protected] > >> http://mail.blueonyx.it/mailman/listinfo/blueonyx > > _______________________________________________ > > Blueonyx mailing list > > [email protected] > > http://mail.blueonyx.it/mailman/listinfo/blueonyx > > _______________________________________________ > Blueonyx mailing list > [email protected] > http://mail.blueonyx.it/mailman/listinfo/blueonyx > > > _______________________________________________ > Blueonyx mailing list > [email protected] > http://mail.blueonyx.it/mailman/listinfo/blueonyx _______________________________________________ Blueonyx mailing list [email protected] http://mail.blueonyx.it/mailman/listinfo/blueonyx
