Am 17.03.2011 02:32, schrieb Lennart Poettering:
> On Thu, 17.03.11 02:21, Mirco Tischler (mircotisch...@gmx.net) wrote:
>>> Your sshd seems to return exit with a non-zero exit code just indicating
>>> a failure of some kind. use "ExecStart=-/foo/bar" instead of
>>> "ExecStart=/foo/bar" to spawn a
On Thu, 17.03.11 02:21, Mirco Tischler (mircotisch...@gmx.net) wrote:
> >> Ok. I'm add corresponding params to kernel cmdline. After sometime i
> >> get on screen messages like in attached image
> > Your sshd seems to return exit with a non-zero exit code just indicating
> > a failure of some kind
Am 17.03.2011 01:13, schrieb Lennart Poettering:
> On Sat, 19.02.11 00:15, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote:
>
> Hmm, can you try to reproduce this when booting with
> systemd.log_level=debug and systemd.log_target=kmsg on the kernel
> cmdline? Then, kmsg should definitely
On Sat, 19.02.11 00:15, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote:
> >> > Hmm, can you try to reproduce this when booting with
> >> > systemd.log_level=debug and systemd.log_target=kmsg on the kernel
> >> > cmdline? Then, kmsg should definitely include a message on what is going
> >> > on. (an
On Fri, 18.02.11 14:27, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote:
>
> On Tue, 2011-02-08 at 13:08 +0100, Lennart Poettering wrote:
> > On Tue, 08.02.11 14:49, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote:
> >
> > > > Oh, intreresting. It's in "failed" state. Can you check syslog/kmsg if
>
On Tue, 2011-02-08 at 13:08 +0100, Lennart Poettering wrote:
> On Tue, 08.02.11 14:49, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote:
>
> > > 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
> > >
On Tue, 08.02.11 14:49, Vasiliy G Tolstov (v.tols...@selfip.ru) wrote:
> > 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
> >
On Tue, 2011-02-08 at 11:50 +0100, Lennart Poettering wrote:
> 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:
> > >
> > > >
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 ss
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 wit
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 tim
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 l
12 matches
Mail list logo
