[2018-11-05 18:21] Giap Tran
> On 18/10/17 16:00:39, Dmitry Bogatov wrote:
> > * messages from wicd proper like 'Autoconnecting...'
> >
> > If I specify --no-{stdout,stderr}, first group of messages will indeed
> > go to standard streams of wicd, but messages from wicd proper will go
> > to /v
Hi Dmitry,
The first, sorry for delay processing,
On 18/10/17 16:00:39, Dmitry Bogatov wrote:
> * messages from wicd proper like 'Autoconnecting...'
>
> If I specify --no-{stdout,stderr}, first group of messages will indeed
> go to standard streams of wicd, but messages from wicd proper will go
Control: tag -1 - moreinfo + upstream
Hi Dmitry,
Dmitry Bogatov wrote:
> > Can you check if these options already help for your needs?
>
> Not exactly. There are two kind of data, that is stored in
> /var/log/wicd/wicd.log:
>
> * stdout/stderr from subprocessed, that wicd executes
> * message
[2018-10-17 02:30] Axel Beckert
> Hi Dmitry,
Hi, Axel
> > please make log file location configurable at run time.
> >
> > In most cases, daemons have option to specify log file location, and
> > providing /dev/stdout fulfils my needs. Wicd, on other hand have path
> > to log file hardcoded in
Control: tag -1 + moreinfo
Hi Dmitry,
Dmitry Bogatov wrote:
> I am working on integrating wicd-daemon with Runit supervision
> system, which assumes logging on stdout.
Cool!
> please make log file location configurable at run time.
>
> In most cases, daemons have option to specify log file loc
Package: wicd-daemon
Version: 1.7.4+tb2-6
Severity: wishlist
Dear Maintainer,
please make log file location configurable at run time. I am working on
integrating wicd-daemon with Runit supervision system, which assumes
logging on stdout.
In most cases, daemons have option to specify log file loc
6 matches
Mail list logo
