Bug 28330 - WRemote upgrade causes xinetd to restart dropping up2date connection
WRemote upgrade causes xinetd to restart dropping up2date connection
Product: Red Hat Linux
Classification: Retired
Component: xinetd (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2001-02-19 13:02 EST by David Lawrence
Modified: 2007-04-18 12:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-20 17:21:50 EST
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 Derek Tattersall 2001-02-19 13:02:58 EST
Being logged in to a box remotely and using up2date to upgrade the box, the
upgrade of xinetd causes the up2date connection to be lost and the upgrade
to not finish.
Comment 1 Trond Eivind Glomsrxd 2001-02-20 14:45:19 EST
I don't see how that is possible, as up2date doesn't use xinetd at all. Adrian?

Comment 2 Trond Eivind Glomsrxd 2001-02-20 17:18:07 EST
(just to clarify, so glen doesn't put this on the must-fix list: The report is
probably bogus).
Comment 3 Adrian Likins 2001-02-20 17:21:46 EST
I cant think of any connection between xinetd and up2date. 
It doesnt start anything from xinetd, or depend on anything
typically launched from xinetd. Coincince, I suspect.
Comment 4 Glen Foster 2001-02-20 17:30:59 EST
Derek, if you can reproduce it, you can re-open it.
Comment 5 Trond Eivind Glomsrxd 2001-02-20 17:33:30 EST
If so, more info must be added so we can find out what is the problem - I can't
see any way it could possibly be xinetd.

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