Ah. I *think* I see what you are getting at, but I'm not at all a code-wrangler, so please correct me if I've misunderstood, or missed your point entirely...
If the utmp/wtmp options are explicitly not compiled in then there's simply no data for the PrintLastLog function to present ?
EDIT:
Doh - I'm blind - I completely missed the --disable-lastlog line outright.
Thanks for the quick answers. 
I would like to enable the SSH PrintLastLog option, so that it displays before the standard MOTD as follows:-
Last login: Sat Mar 23 20:31:23 2024 from 192.168.1.2
##############################################
# LibreELEC #
# https://libreelec.tv #
##############################################
LibreELEC (community): nightly-20240311-86dba4b (Generic.x86_64)
LibreELEC:~ #It's part of the vanilla OpenSSH sshd configuration options and is listed as a commented out flag in LibreELEC's /etc/ssh/sshd_config ...
#PrintLastLog yesThe normal LibreELEC method of supplying sshd overrides via /storage/.cache/services/sshd.conf ...
SSH_ARGS=""
e.g.
SSH_ARGS="-o 'PrintLastLog yes'"... doesn't work. I've tried various ways to quote-encapsulate and supply yes|true|on|=yes|=true|=on type Boolean arguments to the -o options but haven't got anywhere.
Am I just mangling the syntax for a thing that *should* work, or is the LibreELEC sshd compiled without that particular bit of functionality that the regular OpenSSH one has ?
Thanks.
Quick bit of advice needed - before I dive into the rabbit hole of attempting to get a Wayland build of chrome/chromium running on LE12-Generic (NON legacy) ... are there any glaringly obvious STOP signs that more experienced code wranglers are already aware of that would make this a doomed attempt ?
Oops - looks like I raised a half-assed bug report. Sorry 
The issue seems to be with Kodi core, rather than LibreELEC - I lost track of when I switched from LE 11.0 to 12.0 Nightlies.
I had a vague mental note to investigate why the feature wasn't working, but made the assumption it stopped *after* the switch to 12.0. In fact the RSS Ticker isn't working in any of the vanilla Kodi 12 alphas/betas.
[EDIT]
Issue raised at Kodi GitHub: https://github.com/xbmc/xbmc/issues/24229
A long standing issue with Nightly LE12 Generic builds, for at least 3 or 4 months, that I'm finally getting around to looking at.
No changes in the RSS Editor plugin (script.rss.editor - version=4.0.2) or in the /userdata/RssFeeds.xml list that it created.
Parsing the logs I can see that the URL is fetched, but nothing appears on-screen and after a while the session is closed without any further log entries.
debug <general>: Got rss feed: https://feeds.bbci.co.uk/news/world/rss.xml
debug <general>: CurlFile::Open - <https://feeds.bbci.co.uk/news/uk/rss.xml>
debug <general>: Got rss feed: https://feeds.bbci.co.uk/news/uk/rss.xml
...
debug <general>: CheckIdle - Closing session to https://feeds.bbci.co.uk (easy=0x7fc38c01f990, multi=0x7fc38c01eb00)
I've tried it in default skin as well as my normal !Transparency with same result, and all the feeds used are alive and working in a browser session.
Pastekodi log here: rssticker.log (545kB)
All working as expected now - many thanks.
mglae Thanks for that - I'll give 1500 a try.
The 9000MTU jumbo packet setting was just to keep consistent with my Unraid NAS box which has 9000 on it's 10GbE NIC.
To be honest that was an `"temporary experiment" from when I put some NVME cache drives in the server and wanted to see what throughput could be achieved. That was 2 years ago 
It's only a home LAN, and the amount of time the network is really doing any serious transfer is vanishingly small, so I think I'll go back to a 1500MTU network throughout, and not lose any sleep about missing the theoretical 5-10% extra max throughput and the 7 minutes a month it might save me 
Never mind - dug out an old USB 1GbE adapter (also Realtek, as it happens) and a network connection was achieved.
Created the log batch from the Logfiles share - attached here log-2023-12-09-15.40.59.zip (300KB)
The onboard 2.5GbE ethernet devices (eth0 & eth1) both seem to be detected and started without errors that I can see, but for some reason they don't show up in LE/Kodi.
My previously working device on the older nightly builds is eth1.
The temporary 1GbE USB adapter is eth2.
Can anyone see why eth1 isn't working ?
Hi.
Since about mid November the nightly 12.0 Generic builds have resulted in a booted & running LE/Kodi system, but no networking.
Device is an Odroid H3+ (N6005 Celeron) with onboard Realtek RTL8125B (2.5GbE) LAN ports.
The LE settings addon shows no available network devices in Connections.
I tried the "System and Kodi Backup" option in the addon to dump a backup to a removable drive to inspect on another system, but the function doesn't store any useful logs from Kodi or OS.
Given that there seems not to be any method to access a local console shell with attached keyboard in the 12.0 Generic builds I can't access any OS level logs at all to start digging into what exactly is failing.
Any suggestions ?
Was about to report this breaking Multi-Weather addon as trying to display downloaded map gave same _imaging.so error...
Good to see it's already in hand. 
The GitHub pull #7891 [samba: samba-config: call smbpasswd with valid smb.conf] in the latest (20230619-a2c7d54) nightly looks like it's done the trick.
Thank you.
Nope - having 2 memory modules will help performance a *little* on low end/low power machines that have dual channel RAM capability, but Kodi will almost never use more than 2 GB of it.
mglae Thanks for the workaround suggestion.
Yes - the problem seems to be that at boot time the ExecStart=/usr/lib/samba/samba-config initiated from samba-config.service failes to create (or create in time ??) the /run/samba/smbpasswd that smbd is looking for during startsmbfilepwent_internal , so smbd recreates an empty smbpasswd file.
Executing /usr/lib/samba/samba-config later in an SSH session *does* create a proper /run/samba/smbpasswd
So, my question is ... how do I ensure that a populated smbpasswd file is created and|or created in time for smbd to find ?
I'm using LibreELEC-Generic.x86_64-12.0-nightly-20230522-794a8ad, and it's still an issue.
Seems entries in /run/samba/smbpasswd are not persisting after reboot.
I'm getting somewhat lost with the auto-assembly of the final samba config in /run/samba from various other files scattered around the install.
Between /storage/.config/samba.conf , /storage/.kodi/.smb/smb.conf , /storage/.cache/services/samba.conf (and any I've missed) where/what should I be doing so that the smbpasswd username/password entered via LibreELEC-Settings->Services is populated after next boot ?
Cheers,
--
kurai
It's back now - thank you Mysterious Masked Janitor for whatever it was you did. 
This *does* normally work, but the server isn't offering up a download list at the moment.
It occasionally fills up it's diskspace and needs someone to check what it's done and tidy up, as and when they have time.