On Tue, 8 Sep 2015, Andreas Henriksson wrote: > I'm not able to reproduce your problem (only tested on 2.27-1), > but I'm also not using syslog (only journal). This might mean
…okaaay… > that the problem is somewhere in the syslog-specific code Yes, probably. Does this mean that the syslog-specific part of logger(1) is basically unmaintained in Debian? If so, were I to suggest a fix for the other problem with it, would you consider adding it? (The one where when the syslog dæmon is restarted, input is no longer sent to it.) > It's quite simple.... here's a quick tutorial: Thanks. Not “quite”, but doable. > # goto 10 ;-) > In just a few build/reproduce/mark-good-or-bad git will > tell you the exact commit introducing the regression > (via a binary search on the git history). Right, I knew “of” it, but I haven’t ever used it, because all the setup around it is very complex, and the docs are more for people who know the things already. Your quick instructions should help. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
