Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

[Michael Biebl]

Am 18.03.2015 um 16:29 schrieb Robert Pumphrey:

> #!/bin/bash
> ### BEGIN INIT INFO
> # Provides:          iptables
> # Required-Start:    $network $remote_fs $syslog
> # Required-Stop:     $network $remote_fs $syslog
> # Should-Start:      iptables
> # Default-Start:     2 3 4 5
> # Default-Stop:      0 1 6
> ### END INIT INFO


> Also note that the problem is not reproducible if the Provides: and
> Should-Start: name match the init script name, so I guess mismatch in
> the script name and header is at the root of the problem.

The mismatch between init script name and Provides shouldn't be a
problem. You can certainly name your init script foo and have Provides:
bar (the systemd-sysv-generator will then create a bar symlink pointing
at foo).

I think the problem is that you depend on yourself:
Provides: iptables and Should-Start: iptables

This is of course bogus and a bug in the init script, but shouldn't
cause a segfault.

If you remove the # Should-Start:      iptables line, the problem should
be gone.

Now will need to dig into the code, to find the problem.

Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150318/8912301c/attachment-0002.sig>