Bug 10696 - Linuxconf stops sshd
Linuxconf stops sshd
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2000-04-10 09:23 EDT by pfarrell
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:47:39 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 pfarrell 2000-04-10 09:23:09 EDT
Linuxconf stops sshd on activate changes and close all connections

I4m using ssh package from ftp.redhat.de:

Comment 1 Nalin Dahyabhai 2000-04-10 10:59:59 EDT
Does sshd not get restarted?  Or is it that the network interfaces is brought
down and not up for some reason?
Comment 2 Trond Eivind Glomsrxd 2000-04-27 15:21:59 EDT
It just runs the /etc/rc/init/sshd with the argument "stop" - I've no idea of
why, but it did so every time I used linuxconf. This does not happen with the
openssh I'm currently using.
Comment 3 keith.moore 2000-08-17 08:05:55 EDT
In Control Service Activity, turn off Automated, hit Accept, then turn it back
on, and hit Accept.  

I've had a problem where linuxconf gets "out-of-sync" with reality, and if you
let it configure the Start/Stop scripts it gets back into sync.

If you are running it remotely through SSH, just Preview what has been done.  If
it's still trying to stop it, just hit the quit button so it doesn't do it. 

-- Keith Moore

Disclaimer: I do not work for RedHat, my views/responses may or may not reflect
the views of RedHat, Inc.
Comment 4 Brent Fox 2002-06-05 12:11:43 EDT
Closing because we don't ship linuxconf anymore
Comment 5 Red Hat Bugzilla 2006-02-21 13:47:39 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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