|Summary:||LPD ... Cannot bind to lpd port '515'|
|Product:||[Retired] Red Hat Linux||Reporter:||Paul La Marre <pglm>|
|Component:||lpr||Assignee:||Bernhard Rosenkraenzer <bero>|
|Status:||CLOSED WONTFIX||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2004-08-23 19:42:56 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Paul La Marre 2003-04-20 20:52:50 UTC
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; Q312461; .NET CLR 1.0.3705) Description of problem: Boot up error: Startup: LPD ... Cannot bind to lpd port '515' I have seen several comments in the new group "Linux Install" referring to issue. A work around,thanks new group, the issue is to stop the the xinit.d service, starting lpd service and restarting xinit.d. But this does not resolve the boot issue -- only provides a temp solution that must be applied after each reboot. I one and only printer is a "samba" printer. I do not think this is the issue since this is a boot cycle problem -- pre-samba start. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Boot under 9 2. 3. Actual Results: No printer service Expected Results: Printer (lpd) able to load at startup. Additional info:
Comment 1 Paul La Marre 2003-04-30 00:53:45 UTC
Is it possible to change the startup order from: xinetd ntpd lpd to: lpd xinetd ntpd I did a prompted boot In this way xinetd is not started. What effect would such a sequence change have, can it be done manually by editing some ".rc" file? If this is a solution what needs to be changed in the install to make it part of the production release?
Comment 2 Boris Folgmann 2003-09-02 09:18:48 UTC
I updated my LPRng based RedHat 8.0 to 9. Then I switched to CUPS using the printer system switcher. But printing from Windows clients was not possible, though I had changed the printer system in the smb.conf from lprng to cups. :-( Then I switched back to LPRng and now I have this problem here. :-( Bad thing. Where is the official solution for that problem? The report is quite old, isn't it?
Comment 3 Elliot Lee 2004-08-23 19:42:56 UTC
Closing bugs for old packages that have no maintainer.