On Thu, 11 Aug 2016 19:50:09 +, Chris Knadle wrote:
> > But I also started looking at deb-systemd-helper (in
> > init-system-helpers) and found an interesting example:
> >
> > https://sources.debian.net/src/isatapd/0.9.7-2/debian/postinst/?hl=12#L12
> >
> > Maybe this is the way to go?
> >
gregor herrmann:
[...]
> But I also started looking at deb-systemd-helper (in
> init-system-helpers) and found an interesting example:
>
> https://sources.debian.net/src/isatapd/0.9.7-2/debian/postinst/?hl=12#L12
>
> Maybe this is the way to go?
> (And if yes: "disable" or "mask"?)
The code in
On Mon, 01 Aug 2016 19:07:09 +0200, gregor herrmann wrote:
> > Package: dh-systemd
> > [...]
> > Description-en: debhelper add-on to handle systemd unit files
> > dh-systemd provides a debhelper sequence addon named 'systemd' and the
> > dh_systemd_enable/dh_systemd_start commands.
> > .
> >
also sprach gregor herrmann [2016-08-01 19:07 +0200]:
> https://sources.debian.net/src/isatapd/0.9.7-2/debian/postinst/?hl=12#L12
>
> Maybe this is the way to go?
> (And if yes: "disable" or "mask"?)
I think disable inhibits automatic starts, whereas mask prevents
starts
On Sun, 31 Jul 2016 02:16:38 +, Chris Knadle wrote:
> What I think might be helpful here is the dh-systemd package,
> specifically the dh_systemd_enable command:
>
> Package: dh-systemd
> [...]
> Description-en: debhelper add-on to handle systemd unit files
> dh-systemd provides a debhelper
gregor herrmann:
> On Sat, 30 Jul 2016 18:40:21 +, Chris Knadle wrote:
>
> Hi Chris!
:)
> After the upgrade, chosing not to auto-start the daemon, I get this:
>
> So madduck has set START_IODINED to false in /etc/default/iodine
>
> ● iodined.service - A daemon for tunneling
On Sat, 30 Jul 2016 18:40:21 +, Chris Knadle wrote:
Hi Chris!
> >> > After the upgrade, chosing not to auto-start the daemon, I get this:
So madduck has set START_IODINED to false in /etc/default/iodine
> >> > ● iodined.service - A daemon for tunneling traffic over DNS queries
> >> >
gregor herrmann:
> Control: tag -1 + help
>
> On Wed, 27 Jul 2016 13:19:44 +0200, martin f krafft wrote:
>
>> > After the upgrade, chosing not to auto-start the daemon, I get this:
>> >
>> > Setting up iodine (0.7.0-5) ...
>> > Job for iodined.service failed because the control process exited
Control: tag -1 + help
On Wed, 27 Jul 2016 13:19:44 +0200, martin f krafft wrote:
> After the upgrade, chosing not to auto-start the daemon, I get this:
>
> Setting up iodine (0.7.0-5) ...
> Job for iodined.service failed because the control process exited with error
> code.
> See "systemctl
Package: iodine
Version: 0.7.0-5
Severity: serious
After the upgrade, chosing not to auto-start the daemon, I get this:
Setting up iodine (0.7.0-5) ...
Job for iodined.service failed because the control process exited with error
code.
See "systemctl status iodined.service" and "journalctl -xe"
10 matches
Mail list logo