>
> On Thu, Aug 1, 2024 at 8:41 AM Mark Corbin
> wrote:
>
>> Hello
>>
>> I was wondering whether anybody has any experience of running the sshd
>> service successfully on a system with a 'non-bash' shell?
>>
>
> mark, this is a systemd lis
s results in
sshd being unable to get any peer details. The call to getpeername in
service_spawn fails with ENOTCONN.
I can't see anything obvious in either the systemd source that suggests a
dependency on bash.
Any ideas gratefully appreciated.
Regards
Mark
--
*Mark Corbin *
S
On 04/09/2020 22:02, Dave Howorth wrote:
On Fri, 4 Sep 2020 17:59:02 +0200
Lennart Poettering wrote:
On Do, 27.08.20 11:33, Mark Corbin (m...@dibsco.co.uk) wrote:
Hello
I am working on time synchronisation issues at boot for systems
without an RTC (using balenaOS on a Raspberry Pi 3) and
On 04/09/2020 17:19, Lennart Poettering wrote:
On Fr, 28.08.20 14:34, Mark Corbin (m...@dibsco.co.uk) wrote:
For example, when /run/log/journal/d197a2e910964a7f9a0de6462d0d7c62/
contains just 'system.journal' which has all log messages from:
'kernel: Booting Linux on physical
On 28/08/2020 08:06, Ulrich Windl wrote:
Mark Corbin schrieb am 27.08.2020 um 12:33 in
Nachricht
:
Hello
I am working on time synchronisation issues at boot for systems without
an RTC (using balenaOS on a Raspberry Pi 3) and have some questions
about how journald assigns timestamps to log
Hello
I am working on time synchronisation issues at boot for systems without
an RTC (using balenaOS on a Raspberry Pi 3) and have some questions
about how journald assigns timestamps to log messages.
When I boot my system and look at the journal I see an initial date/time
for kernel message
