Bug#926306: RFS: socklog/2.1.0-9
[2019-04-04 13:30] Mathieu Mirmont <mat@parad0x.org>
> > * I know, it is pain, but there should be init.d script. You may want to
> > take a look at bcron=0.11-8.
>
> Sure, no worries. How about systemd service files? It makes little sense
> to run socklog along with systemd I think, but for the principle it may
> be required to profile service files. What do you think?
Up to you. Presence of systemd unit files is not mandated by Policy,
unlike init.d scripts.
> > I believe there should be separate sysuser for socklog-* services.
> > Ideally, separate sysuser for /every/ from socklog-* service, but I do
> > not know, whehter it is possible.
>
> Yeah good point. I tend to think that a single user for all socklog-*
> services would be enough, but if you prefer I can add one user per
> service.
Yes, I'd prefer as much separation, as possible.
> Thanks for the review!
My pleasure. By the way, you seems to forgot to add changelog entry
about new maintainer. Something in lines:
* Set myself as maintainer (Closes: #<orphan-bug-of-socklog>)
--
Note, that I send and fetch email in batch, once every 24 hours.
If matter is urgent, try https://t.me/kaction
--
Reply to: