Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 17788 - Startupposition conflicts with portmap
Startupposition conflicts with portmap
Product: Red Hat Linux
Classification: Retired
Component: glibc (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Jakub Jelinek
Depends On:
  Show dependency treegraph
Reported: 2000-09-22 10:27 EDT by Enrico Scholz
Modified: 2016-11-24 10:27 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-10-03 05:10:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Enrico Scholz 2000-09-22 10:27:55 EDT
syslog makes a connection to localhost, port 111 at startup and waits until
it's established or a timeout occurs.  That's why my startup hangs around 5
minutes at this point.

I am using a @host-entry in /etc/syslog.conf and linux-2.4.0-test8. The
connection attempt can be seen with strace.

I suggest to swap the syslog (12) and portmap (13) startup-positions, so
portmap runs before syslog will be executed.
Comment 1 Bill Nottingham 2000-12-11 17:30:24 EST
It's a change in the kernel's socket behavior.  glibc's RPC stuff
needs tweaked. Alternatively, don't define an NIS domainname
until you run ypbind (this is what the rawhide initscripts and
ypbind will do.)

Assigning to glibc.
Comment 2 Ulrich Drepper 2003-04-21 20:44:30 EDT
Is this still an issue in RHL9?  I very much doubt it.  Please report so that I
can close the bug (or fix the problem).
Comment 3 Ulrich Drepper 2003-10-03 05:10:53 EDT
Closing since I got no reply.

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