Comment 5 for bug 183691

It is important to note that, although it may be possible to restart the CUPS server when it is on the local machine, it is not possible when the server is remote.

It seems to me that it would make more sense to have a framework for restarting the CUPS scheduler automatically in case of a crash (any such case of this being a CUPS bug), so that the user need not know what has happened -- or is prompted for a bug report -- rather than adding UI bits in the wrong place just to deal with bugs.

So my opinion is that what is needed here, if anything, is a 'bug-buddy' for servers, not any extra UI in system-config-printer.