NEW ARMv5te RootFS with Systemd (Please Test)

[Kurlon]

If ntpd is bailing out due to a large difference between reality and what your hardware thinks there are a couple options:

1) Adjust the ntpd start script to include -g as part of the start arguments. This tells ntpd that it's ok to have to make one massive adjustment, just roll with it instead of freaking. Problem is, you have to wait awhile (potentially 4 minutes or more) before ntpd will make that correction as it waits for multiple good polls to remote servers before settling on what the one true chimer status is, so option 2 is:

2) Do a quick adjust first, call ntpd -g -q and wait till that returns, or call ntpdate pool.ntp.org to get your clock quickly in the right ballpark, wait for it to finish, then call ntpd as normal.

[pepedog]

I don't have a problem with ntp myself, but this fakeclock adjusts time to when system was last shut down, so it should help ntpd, plus there may be model A raspberry pi's without network in the future. Also no ntp is installed by default, just because arch x86 doesn't, well they all (probably) have RTC's

[pennguin]

Finally I had time to test new RootFS on GoFlexNet with new uboot, I don't see any issues all seems to be working.

[pepedog]

One thing with your rootfs, halt or reboot doesn't shut down an sash session for quite awhile even though it's powered down, the rootfs I made its almost instant

[Kurlon]

$this->bbcode_second_pass_quote('pepedog', 'O')ne thing with your rootfs, halt or reboot doesn't shut down an sash session for quite awhile even though it's powered down, the rootfs I made its almost instant

[pepedog]

With systemd, this is first time for me, all other devices I have, inc my own rootfs on dockstar is quick to discon

[WarheadsSE]

I've seen this same behavior. It essentially isn't nicely informing the sessions that it is closing the socket & ending the session.

[sputnik]

Thank you xenoxaos. It works absolutely great on my Dockstar, no muss no fuss.
Oh, I didn't mean getting all the daemons converted over, but they were 99% easy too. That 1% though, it'll get ya.
Rtorrent w/Dtach -n. Dtach creates a session then exits, wonderful that's what it's supposed to do, call it up when you want. But systemd thinks everything has quit. Gotta read them manuals some more
Anyhow, plenty of time to fix that, otherwise 100% pure systemd here, no issues in 2 days.
Using LVM, samba, openssh-cryptodev, openvpn, openntpd, asterisk, fail2ban, iptables and of course, rtorrent.

[WarheadsSE]

make sure the Rtorrent .service file is set to Type=forking

[sputnik]

Thank you WarheadsSE, as usual, you're always right on top of it.
I did that, and all others, but mostly forking.
RemainAfterExit=yes, all sorts of things.
But don't waste thought on it, I'll find the answer & post it.
Kinda special, this dtach thing, nothing quite like it, have perused many, many examples on the web.
There are examples others have had success with using screen & tmux, but I suspect they are actually opening a terminal instance, here I don't want to open at all, just have rtorrent run, open when I feel like it, as I have done in the past.