Tincd does not write log messages to syslog. Asking the upstream developers the problem comes with some wrong command line options used in the init script. Those command line options should be used only for debug purposes. I would recommend removing the --logfile option, and the --pidfile option also, because it is redundant. Reproducible: Always Steps to Reproduce: ps aux | grep tincd and you can see that tincd is running with --logfile and --pidfile Expected Results: Software should write messages directly to syslog
> Software should write messages directly to syslog There are many programs that use specific /var/log/... and most of them - and tinc too - allow to choose if syslog or dedicated file are better for their needs. It is better for me to have dedicated tinc logs, because I need to know how much time I spent on VPN to every institution. I can see two solutions: 1. adding "syslog" USE flag to ebuild which cause tinc daemon use it (by removing --logfile from init scripts) 2. a way to change it's behavior from config file - /etc/conf.d/tincd I think (1) is much better and so I will introduce in bleeding-edge. (where there is tinc-1.0.14 since 11-th of May - I wrote Daniel Black about it)
Created attachment 283897 [details, diff] version bump to 1.0.16 and syslog USE flag added to ebuild
Created attachment 283899 [details] gpg signature of attached patch
I attach the patch that updates the ebuild to version 1.0.16 and creates the syslog USE flag. It is my first ebuild, I checked that it works fine, maybe is not very clean about gentoo syntax conventions.
I just adopted this package and bumped it to 1.0.16, latest upstream stable. I did not add anything new ... yet. I'm getting a feeling for the package first. Can you give me your stuff in comment 2 as patches against the initrd image and the ebuild that will hit the tree in a few minutes. Please don't post the manifest or your gpg sig as those are not necessary. Also seperate each file into its own patch. Thanks for your contribution :)
Created attachment 287565 [details, diff] Introduce the syslog USE flag
Created attachment 287567 [details, diff] adds initd script when USE flag syslog enabled
Created attachment 287569 [details, diff] adds initd script when USE flag syslog disabled
Hello, just to clarify, the file tincdnosyslog is exactly the same file of tincd initrd image present in the ebuild the tincdsyslog is different just for one line. the ebuild selects which one of the two files to install depending on the 'syslog' USE flag.
(In reply to comment #6) > Created attachment 287565 [details, diff] > Introduce the syslog USE flag I see what you're trying to do here, but it bothers me that we have to introduce two nearly identical files. I'm going to see if there's another way. Also there is a small oversight in your patch. The line just before your if use syslog installs both tincd and tincd.lo. Since your if does that, you also want to change the line doinitd "${FILESDIR}"/tincd{,.lo} to just doinitd "${FILESDIR}"/tincd.lo Don't resubmit since I'm going to try to do this in a more economical way.
(In reply to comment #1) > > Software should write messages directly to syslog > > There are many programs that use specific /var/log/... and most of them > - and tinc too - allow to choose if syslog or dedicated file are better for > their needs. > It is better for me to have dedicated tinc logs, because I need to know how > much > time I spent on VPN to every institution. > > I can see two solutions: > 1. adding "syslog" USE flag to ebuild which cause tinc daemon use it > (by removing --logfile from init scripts) > 2. a way to change it's behavior from config file - /etc/conf.d/tincd > > I think (1) is much better and so I will introduce in bleeding-edge. > (where there is tinc-1.0.14 since 11-th of May - I wrote Daniel Black about it) Okay I'm going with option 2. This is the obvious way of doing it. The USE flag is bad design because it means having to recompile tinc in order to change behavior rather than just changing one line in conf.d/tincd. I'll have something up in a day or so. Please test tinc-1.0.16-r1 and report back to this bug.
(In reply to comment #11) > I'll have something up in a day or so. Please test tinc-1.0.16-r1 and report > back to this bug. Its up. Please test since this represents a significant rewrite of the init script system, making it more compliant with openrc. I also took the opportunity to change some variable names to match those of the documentation, notably, TINCNET was changed to NETNAME (see man tincd).
I upgrade to net-misc/tinc-1.0.16-r1 looks good to me :)
Please reopen if there's any further issues.
