Thorben T.
Thorben T.
do we also want a pidfile, or is logging sufficient?
also, now that we have `--foreground`, this is much less critical.
if you want to confuse yourself with the full history of this, read #40 #93 #94 . specifically https://github.com/volkszaehler/vzlogger/issues/94#issuecomment-75153851
@dmesser: i'm only trying to point out that the issue arises because vzlogger gives a different meaning to "daemon" - which may very well be a bug.
imho, it would make more sense to have a single ticket to fix the whole thing to conform to usual conventions, instead of single tickets demanding new features. this would...
@juergen4mueller: the documentation bug is also known already. https://github.com/volkszaehler/vzlogger/issues/94#issuecomment-84257539 as you can see if you read the discussion, this issue is kind of deadlocked, with no developer picking it up...
(the trivial part of ditching "daemon" and adding foreground mode is now in #450 .) single-shot mode is actually quite a bit more complex. as pointed out in https://github.com/volkszaehler/vzlogger/issues/389#issuecomment-520240820 ,...
for anybody feeling extremely adventurous, #450 has an implementation of single-shot mode now, i tested this ONLY with protocol=random and api=null so far. if you try anything else and it...
@mbehr1: maybe you can help, it seems you wrote most of the unit-tests: my changes add a dependency on the `options` global to MeterS0.cpp, (so that if if single-shot mode...
> add warning for S0 meters when addmode != sum for the impulse channel, NOT for the power channel!