Systemd catches up with bind events

This is interesting and further enforces my half formed thought that matching of inverse patterns are bad since it assumed that the set of values är fixed and unchanged.

The example in the article was matching
~add|change when what is needed is remove.

For this poster the problem sounds like the reverse, he needs to match ~add|change and someone have "optimzed" that to remove.

This proves that one need to know what one is doing and that crap can be written in any language, in this case the udev config rule language.

One way to fix this is to document an ERROR event.
Any rule that mentions an ERROR event is broken.
Any action that happens when ERROR is issued is a bug.