Bug 123560 - gimp-print-cups %post starts cupsd in Anaconda
gimp-print-cups %post starts cupsd in Anaconda
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: gimp-print (Show other bugs)
3.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-19 08:25 EDT by Jos Vos
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-05-19 09:32:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jos Vos 2004-05-19 08:25:48 EDT
Description of problem:
The %post section of gimp-print-cups does a "cups reload".  Even
during an initial install, this actually starts cupsd, that dies after
a while, but it delays the install for several minutes.

Version-Release number of selected component (if applicable):
gimp-print-cups-4.2.4-5

Solution:
As there is no "condreload", the "cups reload" should be replaced by a
"cups condrestart", IMHO.

Additional info:
I have seen this problem on an own RHEL3 rebuild, I do not know for
sure if RHEL3 includes the gimp-print-cups subpackage.
Comment 1 Tim Waugh 2004-05-19 08:30:23 EDT
This is entirely intentional.  The delay has to happen some time: it's
better at package install than at next boot.
Comment 2 Jos Vos 2004-05-19 08:42:48 EDT
Are you seriously saying that is is intentionally to *start* cupsd *in
Anaconda* (which is what happens now)?  I don't know why cupsd died
after a few minutes, but it was also eating nearly 100% CPU time, more
or less stopping the install (I'm not sure if the %post script was
still running, forgot to check, but the install only proceeded after
cupsd died).

A simple check on /var/lock/subsys/cups would also help...
Comment 3 Tim Waugh 2004-05-19 09:32:56 EDT
Yes, this is intentional, as I mentioned in comment #1.

It is building the PPDs database (and exiting), using the --ppdsdat
option.

Note You need to log in before you can comment on or make changes to this bug.