Re: Syslog logging in client
> On Wed 2/12/2015, at 3:10 am, Konstantin Tokarev wrote: > Implemented here: > https://github.com/mkj/dropbear/pull/18 > > However, I didn't add command line option. I thought it may be better to use > -o, but it has 2 issues currently: > > * -o patch was not approved yet > * There's no corresponding OpenSSH option, so it may require > "vendor-prefixing", like DropbearUseSyslog or DbclientUseSyslog Thanks, from a first look over that patch looks good. I think "-o usesyslog" is safe enough. I won't merge these new features until after 2015.71 in a day or so - bugfixes only for now. Cheers, Matt
Re: Syslog logging in client
30.11.2015, 16:19, "Matt Johnston" : >> On Mon 30/11/2015, at 8:38 pm, Konstantin Tokarev wrote: >> >> Hi all, >> >> I think it would be useful to have syslog loggin in client when it is >> running in background (e.g., when -f option is used, or, like in my case, it >> is started from init system to create tunnel). >> >> Would such contribution be welcome? > > That sounds useful. Another related thing I've been meaning to add is "-P > pidfile" for dbclient -f, so the client can be killed. (I'm not suggesting > you work on that, just as a thought). Implemented here: https://github.com/mkj/dropbear/pull/18 However, I didn't add command line option. I thought it may be better to use -o, but it has 2 issues currently: * -o patch was not approved yet * There's no corresponding OpenSSH option, so it may require "vendor-prefixing", like DropbearUseSyslog or DbclientUseSyslog -- Regards, Konstantin
Re: Syslog logging in client
30.11.2015, 16:19, "Matt Johnston" : >> On Mon 30/11/2015, at 8:38 pm, Konstantin Tokarev wrote: >> >> Hi all, >> >> I think it would be useful to have syslog loggin in client when it is >> running in background (e.g., when -f option is used, or, like in my case, it >> is started from init system to create tunnel). >> >> Would such contribution be welcome? > > That sounds useful. Another related thing I've been meaning to add is "-P > pidfile" for dbclient -f, so the client can be killed. (I'm not suggesting > you work on that, just as a thought). I was missing this feature once, but now I also need to restart dbclient after exit, so it won't help anyway. -- Regards, Konstantin
Re: Syslog logging in client
> On Mon 30/11/2015, at 8:38 pm, Konstantin Tokarev wrote: > > Hi all, > > I think it would be useful to have syslog loggin in client when it is running > in background (e.g., when -f option is used, or, like in my case, it is > started from init system to create tunnel). > > Would such contribution be welcome? That sounds useful. Another related thing I've been meaning to add is "-P pidfile" for dbclient -f, so the client can be killed. (I'm not suggesting you work on that, just as a thought). Cheers, Matt
Syslog logging in client
Hi all, I think it would be useful to have syslog loggin in client when it is running in background (e.g., when -f option is used, or, like in my case, it is started from init system to create tunnel). Would such contribution be welcome? -- Regards, Konstantin