On Wed, Feb 23, 2011 at 06:23:05PM +0100, Lennart Poettering wrote:
> On Wed, 23.02.11 16:24, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
>
> > Hi,
> > I wanted to see what happens when using per-connection sshd@.service
> > from http://0pointer.de/public/systemd-units/sshd@.service.
>
On Wed, 23.02.11 16:24, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> Hi,
> I wanted to see what happens when using per-connection sshd@.service
> from http://0pointer.de/public/systemd-units/sshd@.service.
>
> After doing some ~1200 ssh connections, the socket went into
> disabled sta
On Tue, Feb 22, 2011 at 02:17:02PM +0300, Alexey Shabalin
wrote:
> >> For replace rc.sysinit, may be make like rc.sysinit:
> >> first run multipath, second mdadm, and last lvm services.
> >
> > That is exactly what fedora-storage-init does. Why not simply use it then?
> > :)
> >
> Yes, did so.
>
On Wed, 23.02.11 09:43, Mike Kazantsev (mk.frag...@gmail.com) wrote:
> > CPUShares=2048
> > CPUSetCPUs=2,3
> >
> > which would implicitly add "cpu" and "cpuset" to the list the user can
> > otherwise control with ControlGroup=, and then write "2048" resp. "2,3"
> > to the cpu.shares resp. cpuset.
Hi,
I wanted to see what happens when using per-connection sshd@.service
from http://0pointer.de/public/systemd-units/sshd@.service.
After doing some ~1200 ssh connections, the socket went into
disabled state:
Feb 23 15:43:23 fedora systemd[1]: sshd.socket failed to queue socket startup
job: File
On Wed, 23 Feb 2011 12:48:10 +0500
Mike Kazantsev wrote:
> There seem to be some problems (timeout) on shutdown though (which I
> need to investigate, but pretty sure something hangs on /dev/log), so
> this doesn't seem to be a perfect solution either.
Scratch that, I just forgot to add Conflict
