Bug 50073
Summary: | test page cannot be printed until lpd is restarted | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <urban> |
Component: | printconf | Assignee: | Crutcher Dunnavant <crutcher> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-08-02 08:48:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2001-07-26 14:57:57 UTC
agreed. Test functionality will be aware of this problem in the next version. oops. after I wrote this it was clear to me that someone wishing to interpret my report in the narrowest possible fashion might conclude that the fix is to change the behavior of the "test-page" option. The problem is that lpd needs to be restarted after configuring this printer (and probably any printer, but I don't know that). Thus the fix is to have the print-tool *automagically* restart lpd as the last step of the configuration. That is what I meant by "the config-tool should know this". The failure of the "test-page" option is a symptom, not the disease. no. restarting lpd is expensive. you have to rebuild queues, and I dont want to be thrashing the system when a knowledgeable user sits down to add 20 printers. I thought about this for a while, and there are several internal oppinions, but this is the way I am going. But test page printing does force a restart now. umm. I agree that a forced restart after adding every new printer is not very clever, but it seems to me that allowing a user to create a printer he can't use until he's restarted lpd is also not very clever (if you don't tell him that). There are other possibilities besides a blind restart or no blind restart. I have two suggestions. Either: A) pop up a diagog box with a nice little message ("you must restart lpd before this printer can be used") B) check whether a restart is necessary at tool-exit, and either do it, or tell the user. Silent failure isn't really what you want, is it? I am not doing either. a) I'd have to pop up this little dialog after /every/ change. People only have to learn this once, and I'm not writing nag-ware. b) Users are permitted to change their minds. I will not save changes or restart lpd without their concent. |