On 01/22/15 03:32, CLOSE Dave wrote:
Ed Greshko wrote:
You probably will want to follow this procedure in F21
https://access.redhat.com/solutions/1166283
Thanks. That works perfectly in F20.
So we appear to have confirmed that the default installation is broken
in SysV versions (mine
On Tue, Jan 20, 2015 at 04:32:40PM -0800, Rick Stevens wrote:
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
-
I'd like to run two SSH daemons on the same machine. They will listen on
different ports and have other differences in their configuration. I
want these two daemons to be independent of each other: either can run
while the other is stopped. I need to do this for recent (systemd)
machines and
On 01/21/15 08:20, CLOSE Dave wrote:
I'm finding that, although the SSH daemon records its PID in a file,
that file is not configurable. Consequently, it seems that stopping one
of the daemons causes the other to also stop. Same for starting one.
Look in /etc/ssh/sshd_config and notice
On 01/20/2015 04:20 PM, CLOSE Dave wrote:
I'd like to run two SSH daemons on the same machine. They will listen on
different ports and have other differences in their configuration. I
want these two daemons to be independent of each other: either can run
while the other is stopped. I need to do
On 01/20/2015 06:20 PM, CLOSE Dave wrote:
I'm finding that, although the SSH daemon records its PID in a file,
that file is not configurable. Consequently, it seems that stopping one
of the daemons causes the other to also stop. Same for starting one.
There is a PidFile option in the config
Ed Greshko wrote:
But if you read the SSHD man page and the /etc/rc.d/init.d/sshd script,
you'll find that the PID is always recorded at /var/run/sshd.pid and the
PidFile variable is only used for reporting status.
And if you tried it?
[root@meimei run]# grep pid /etc/ssh/sshd_config
Ian Pilcher and others wrote:
There is a PidFile option in the config file that can be used to
control this.
But if you read the SSHD man page and the /etc/rc.d/init.d/sshd script,
you'll find that the PID is always recorded at /var/run/sshd.pid and the
PidFile variable is only used for
On 01/21/15 09:06, CLOSE Dave wrote:
Ian Pilcher and others wrote:
There is a PidFile option in the config file that can be used to
control this.
But if you read the SSHD man page and the /etc/rc.d/init.d/sshd script,
you'll find that the PID is always recorded at /var/run/sshd.pid and the
On 01/21/15 10:34, CLOSE Dave wrote:
Ed Greshko wrote:
Well, I don't seem to be telling you. I'm actually showing you.
:-) :-)
Yes, and thank you. But you didn't explicitly mention the version. In my
original note, I said I'd only tried SysV. Before I make the effort to
do it on systemd, I
Ed Greshko wrote:
Well, I don't seem to be telling you. I'm actually showing you.
:-) :-)
Yes, and thank you. But you didn't explicitly mention the version. In my
original note, I said I'd only tried SysV. Before I make the effort to
do it on systemd, I thought it would be worth asking for
On 01/21/15 10:01, CLOSE Dave wrote:
I have tried it. At least on an earlier Fedora with SysV.
FWIW, the problem you're having with sshd and SysV has to do with how the init
scripts are constructed.
They source /etc/rc.d/init.d/functions which includes the functions
pidfileofproc and
On 01/21/15 10:01, CLOSE Dave wrote:
Ed Greshko wrote:
But if you read the SSHD man page and the /etc/rc.d/init.d/sshd script,
you'll find that the PID is always recorded at /var/run/sshd.pid and the
PidFile variable is only used for reporting status.
And if you tried it?
[root@meimei
On 01/21/15 10:01, CLOSE Dave wrote:
I'll try F21 soon.
You probably will want to follow this procedure in F21
https://access.redhat.com/solutions/1166283
--
If you can't laugh at yourself, others will gladly oblige.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or
14 matches
Mail list logo
