On Wed, Nov 17, 2010 at 08:21:03AM +0100, Andrew Beekhof wrote: > On Tue, Nov 16, 2010 at 2:27 PM, Dejan Muhamedagic <[email protected]> > wrote: > > Hi, > > > > On Mon, Nov 15, 2010 at 06:18:29PM +0100, Bernd Schubert wrote: > >> On Monday, November 15, 2010, Dejan Muhamedagic wrote: > >> > > > This may truncate entity, and of course breaks existing filtering > >> > > > setups that trigger on it. > >> > > >> > Right. So, this needs to be optional. > >> > >> Ok, any favourite option keyword in logd.cf? If it comes to me, the present > >> logd.cf *suggests* that not adding the commong log entity is a bug: > >> > >> <quote> > >> # Entity to be shown at beginning of a message > >> # for logging daemon > >> # Default: "logd" > >> entity logd > >> </quote> > >> > >> Was that option only for its own messages? > > > > Yes, and the default in case the client didn't supply its entity. > > > >> Isn't that a bit over-due? > > > > I guess you meant overkill? Perhaps. > > > >> So maybe > >> "entity none" should suppress it in the future? > > > > We can't change the semantic. So, we need a new option name. > > extra_entity? common_entity? > > fwiw, syslog_facility works the way Bernd proposed
It does not, at least not if you don't have it exclusively. That has been his starting point. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________________ Linux-HA-Dev: [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev Home Page: http://linux-ha.org/
