On Jan 17, 2008 9:56 AM, Tim Waugh <[EMAIL PROTECTED]> wrote: > 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. > Agreed.
> > 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. > Yeah. Adding UI is essentially doing the same thing and still not solving the problem too much. To make things easier, I'd say we just need to automate the task of restarting the server in case of problem. Maybe a refresh button that restarts the server in the background might be a good UI decision although better automation might make such UI changes unnecessary > > 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. > > -- > [GUI] Allow user to 'restart', 'stop' and 'start' /etc/init.d/cupsys via > system-config-printer > https://bugs.launchpad.net/bugs/183691 > You received this bug notification because you are a direct subscriber > of the bug. > -- [GUI] Allow user to 'restart', 'stop' and 'start' /etc/init.d/cupsys via system-config-printer https://bugs.launchpad.net/bugs/183691 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
