Method of stopping system cupsd to run printing test fails on Rawhide

[Jeff Johnson]

Yesterdays run of printing test reported "There are problems". Verbose log
shows:

[01:43:26] Package 'lsb-test-printing' v. '*' (4.1.0-2) is installed.
[01:43:26] %> rm -rf '/opt/lsb/test/printing/results'/*
[01:43:26] %> ps -A | grep -e '\<cupsd$'
[01:43:26] | 537 ? 00:00:00 cupsd
[01:43:26] %> ps -A | grep -e '\<cupsd$'
[01:43:26] | 537 ? 00:00:00 cupsd
[01:43:26] %> killall cupsd
[01:43:28] %> ps -A | grep -e '\<cupsd$'
[01:43:30] | 537 ? 00:00:00 cupsd
[01:43:30] %> killall -9 cupsd
[01:43:32] %> ps -A | grep -e '\<cupsd$'
[01:43:32] | 16192 ? 00:00:00 cupsd
[01:43:32] !!! ERROR:
[01:43:32] Failed to prepare printing. The test will be skipped
[01:43:32] Failed to stop cups daemon
[01:43:32] Failed to stop 'cupsd'

Logging into the system, I see cupsd is run with -f (foreground), and manually
killing it like the test attempts to do a see it eventually respawn.

cups-1.5.0-24.fc17.i686

So it looks like we'll have to approach this differently, perhaps have
dist-checker check this state initially with the various testing requirements
and have the user stop the cups daemon (however it's to be stopped these days,
chkconfig gives a very abbreviated list of services pointing to using systemd)
before any testing proceeds (if printing is selected).

Looking at the systemd docs on the fedora wiki, it suggests that systemctl is
the way to control these things now but...

systemctl stop cups.service

followed by

systemctl status cups.service

But then it again respawns and status shows it running