Bug 29493 - running up2date through sshd, kills sshd when updateing
running up2date through sshd, kills sshd when updateing
Product: Red Hat Linux
Classification: Retired
Component: openssh (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2001-02-25 19:39 EST by Rod m. Stewart
Modified: 2015-01-07 18:44 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-02-27 18:31:55 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 Rod m. Stewart 2001-02-25 19:39:40 EST
If you run 'up2date --nox -u' from remote through an sshd connection, your
connection dies when it updates the openssh-server rpm.  At least going
from fisher to wolverine it does.   This would seem to me to be something
many people would do, as I don't usually want to log onto the console of
every machine I have to run up2date.

One other thing I noticed was that sshd did not restart, I had to go
upstairs and restart it on the server manually.

Not certain if this is up2date or openssh related.
Comment 1 Glen Foster 2001-02-26 18:50:29 EST
This defect is considered MUST-FIX for Florence Release-Candidate #2
Comment 2 Adrian Likins 2001-02-27 15:42:56 EST
Isnt this an issue with the openssh packages? Shouldnt they
be handling the "update" themselves?  

I dont  know anything that up2date would be doing, or
could be doing to prevent this.
Comment 3 Preston Brown 2001-02-27 18:31:51 EST
this is an openssh issue, but I don't know if it can be changed.
Comment 4 Nalin Dahyabhai 2001-02-28 11:27:12 EST
IIRC this was due to some changes in the way initscripts would restart
services.  I believe that this is fixed in the current tree (I have
experimentally verified this, too).  Please reopen this bug if you find that
this continues to be a problem with initscripts-5.65 and later.

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