Bug 837590
Summary: | service cups start too quickly and cups can not be ready for following command | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Petr Sklenar <psklenar> |
Component: | cups | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Sklenar <psklenar> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 | CC: | azelinka, jpopelka, psklenar |
Target Milestone: | rc | Keywords: | Regression |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-06-20 12:18:34 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Petr Sklenar
2012-07-04 10:25:41 UTC
Petr: I haven't been able to reproduce this. What you run 'service cups stop', what output do you get? What about when you run 'lpstat -p' at that point (after you've stopped the service)? What does 'systemctl status cups.socket' say? it does not produce any issue now: https://beaker.engineering.redhat.com/jobs/438144 I guess it was somehow solved by systemd , tried RHEL-7.0-20130606.0 Server x86_64 |