I reread after quite some time what course discussion here plots now .. I'm almost completely with johannes (and his kind of voices) .. the only sane solution is to not overcomplicating it by trying to do it systemd-smart (what is not probably exactly "smart" for everyone) until this part of systemd gets some design improvements (and this rule can by apply generally on every second systemd feature) .. just plain cupsd.service (like in good old times) spawning cupsd process reading its own configuration in cupsd.conf works and is clear enough .. I don't really catch what all have happened here during the life of this bugreport .. regards, d