On Tue, 08.02.11 13:41, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote: > > On Tue, 2011-02-08 at 11:09 +0100, Lennart Poettering wrote: > > On Mon, 07.02.11 18:49, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote: > > > > > Hello. I'm new in this list. > > > I'm using systemd-17. I'm try to use sshd.socket and sshd@.service (run > > > sshd in inetd mode). After i'm start service with systemctl start > > > sshd.socket i'm able to connect. But after some time (for example > > > disconnecting) sshd not respond. netstat -nal says, that nobody listens > > > 22 port. After i do systemctl start sshd.socket connection can be > > > established.... > > > > Hmm, what does "systemctl status sshd.socket" say when this happens? > > Normally systemd should continue listening until sshd.socket is shut > > down and spawn sshd@xxxx.service for every connection. > > > > Lennart > > > > status says: > > Loaded: loaded (/lib64/systemd/system/sshd.socket) > Active: failed since Mon, 07 Feb 2011 22:36:51 +0300; 15h ago > Accepted: 1596; Connected: 0 > CGroup: name=systemd:/system/sshd.socket
Oh, intreresting. It's in "failed" state. Can you check syslog/kmsg if systemd generated any kind of log output when this happened? i.e. around Mon, 07 Feb 2011 22:36:51 +0300. This should give us a hint on what might be wrong. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
