Hello,
Maxim Cournoyer skribis:
> Ludovic Courtès writes:
>
> [...]
>
>>> I'm not sure. The beauty of Shepherd, in my eyes, when compared to
>>> other init systems, is that it is lean and clean. Leveraging what's
>>> already out there (and part of GNU) seems an obvious path to me, as it:
>>>
Hi Ludovic!
Ludovic Courtès writes:
[...]
>> I'm not sure. The beauty of Shepherd, in my eyes, when compared to
>> other init systems, is that it is lean and clean. Leveraging what's
>> already out there (and part of GNU) seems an obvious path to me, as it:
>>
>> 1. Means less code to write,
Hi,
Maxim Cournoyer skribis:
> Ludovic Courtès writes:
>
> [...]
>
>> sshd could also be started via socket activation; ‘sshd’ subprocesses
>> corresponding to existing logins would be unaffected.
>>
>>> Also, it seems to me inetd can already do "socket activation", if this
>>> was somehow usef
Hi Ludovic,
Ludovic Courtès writes:
[...]
> sshd could also be started via socket activation; ‘sshd’ subprocesses
> corresponding to existing logins would be unaffected.
>
>> Also, it seems to me inetd can already do "socket activation", if this
>> was somehow useful.
>
> Yes, inetd can do that
Hi,
Maxim Cournoyer skribis:
>>> I was just kicked out of my own server due to this PAM/SSH issue. It
>>> happens quite frequently here. Time for a fix :).
>
> Not a meaningful contribution to the discussion, but my workaround is to
> disable PAM; as it is not enabled in OpenSSH by default, perh
Hello,
Ludovic Courtès writes:
> Hi,
>
> Mathieu Othacehe skribis:
>
>>> This sounds a lot like this:
>>>
>>> https://issues.guix.gnu.org/32182#1
>>
>> I was just kicked out of my own server due to this PAM/SSH issue. It
>> happens quite frequently here. Time for a fix :).
Not a meaningful c
Hi,
Mathieu Othacehe skribis:
>> This sounds a lot like this:
>>
>> https://issues.guix.gnu.org/32182#1
>
> I was just kicked out of my own server due to this PAM/SSH issue. It
> happens quite frequently here. Time for a fix :).
Note that ‘guix deploy’ now opens a single SSH session, starting
> Regarding the two potential solutions that you proposed in 2018, are
> they still actual? If yes, I could maybe try to implement the second
> suggestion: introducing service chain-loading.
Oh sorry, I stopped reading the thread at
https://issues.guix.gnu.org/32182#1. Looks like the service
cha
Hey,
> This sounds a lot like this:
>
> https://issues.guix.gnu.org/32182#1
I was just kicked out of my own server due to this PAM/SSH issue. It
happens quite frequently here. Time for a fix :).
Regarding the two potential solutions that you proposed in 2018, are
they still actual? If yes, I
Hi,
Maxim Cournoyer skribis:
> Following the big merge of the core-updates-frozen branch into master,
> I've noticed now on two counts the following: running 'guix deploy'
> leaves the remote machine unreachable by SSH. The connection passes
> authentication but then gets closed immediately. /
Hello,
I've found a workaround: disabling PAM for the remote machine
ssh-daemon. This is not done as part of 'guix deploy', so needs to be
fiddled with manually; I did it this way:
1. take note of the command line and sshd_config file:
--8<---cut here---start
Hello Guix!
Following the big merge of the core-updates-frozen branch into master,
I've noticed now on two counts the following: running 'guix deploy'
leaves the remote machine unreachable by SSH. The connection passes
authentication but then gets closed immediately. /var/log/messages
reveals th
12 matches
Mail list logo
