Re: [systemd-devel] How to securely load a firewall before networking gets up?

On Thu, 28.07.16 17:29, Patrick Schleizer (patrick-mailingli...@whonix.org) wrote: > TLDR: > > How to securely load a firewall before networking gets up? > > Can you provide a secure, recommended or even canonical example of such > a firewall.service? See

Re: [systemd-devel] enable/disable swap before/after hibernation

> If clients ask logind whether hibernation is available or try to > initiate hibernation we check whether swap is available and refuse > if it isn't. This means if you add the swap only after the > hibernation was already initiated then this will not be able to > affect the check anymore. I

Re: [systemd-devel] Where is systemd non-devel list?

On Thu, 28.07.16 17:52, Chip (jeffsch...@gmail.com) wrote: > I see that my question re: issues with systemd, is more suited for non > development list. > > Is there a non development systemd list? There is none for now. Just use the -devel list. As long as the noise doesn't get too bad we'd

Re: [systemd-devel] hardware clock

On Wed, 27.07.16 19:54, Michał Zegan (webczat_...@poczta.onet.pl) wrote: > Hello. > > There is, it seems, a problem with the hardware clock. That is, the > systemd does not care about it. Neither systemd nor udev rules set the > system time using the hardware clock. > From what I know, if the

Re: [systemd-devel] No rhyme or reason to systemd enabling/disabling service

On Thu, 28.07.16 13:44, Chip (jeffsch...@gmail.com) wrote: > Ubuntu 16.04 > > With no changes to software or anything, on reboot, systemd *sometimes* will > start dnscrypt-proxy.service while other times just ignores it and it fails > to start. There is no rhyme or reason as to why sometimes it

Re: [systemd-devel] enable/disable swap before/after hibernation

On Thu, 28.07.16 19:25, Lukas Pirl (syst...@lukas-pirl.de) wrote: > Dear list, > > I want to enable/disable the swap partition before/after hibernation. > > However, it seems I cannot get the service to run early enough to avoid > the error: > > Failed to hibernate system via logind: Sleep

Re: [systemd-devel] systemd-nspawn and shared private network

On Thu, 28.07.16 20:19, Igor Bukanov (i...@mir2.org) wrote: > Hello, > > I am trying to see how to implement with systemd-nspawn a version of > docker's pod when a group of very lightweight containers use a > loopback interface or unix sockets to communicate with each other and > a shared

Re: [systemd-devel] No rhyme or reason to systemd enabling/disabling service

On 07/29/2016 05:57 AM, Lennart Poettering wrote: On Thu, 28.07.16 13:44, Chip (jeffsch...@gmail.com) wrote: Ubuntu 16.04 With no changes to software or anything, on reboot, systemd *sometimes* will start dnscrypt-proxy.service while other times just ignores it and it fails to start. There

Re: [systemd-devel] How to securely load a firewall before networking gets up?

Thank you! I forwarded your review in form of bug reports to the affected projects. [1] [2] Lennart Poettering: > On Thu, 28.07.16 17:29, Patrick Schleizer (patrick-mailingli...@whonix.org) > wrote: > >> TLDR: >> >> How to securely load a firewall before networking gets up? >> >> Can you

Re: [systemd-devel] systemd-nspawn and shared private network

Lennart Poettering wrote: > One option could be to add --same-network= or so to nspawn It seems it would be better to refer to the service unit that executed nspawn, not the container running in the namespace created with nspawn. This way I can refer to that unit using a stable name. Another

Re: [systemd-devel] No rhyme or reason to systemd enabling/disabling service

On 29/07/16 16:59, Chip wrote: > On 07/29/2016 05:57 AM, Lennart Poettering wrote: >> My educated guess is that some cyclic dependency or so caused it to >> not be considered for activation at boot. Lennart's guess was correct: > Jul 29 11:33:06 blablabla systemd[1]: basic.target: Found ordering

Re: [systemd-devel] Where is systemd non-devel list?

On Fri, Jul 29, 2016 at 5:52 AM, Lennart Poettering wrote: > On Thu, 28.07.16 17:52, Chip (jeffsch...@gmail.com) wrote: > > > I see that my question re: issues with systemd, is more suited for non > > development list. > > > > Is there a non development systemd list? > >

Re: [systemd-devel] No rhyme or reason to systemd enabling/disabling service

On 29/07/16 18:46, Chip wrote: > And I believe, yes, network must be operating before > dnscrypt-proxy activates. I'm guessing that some configuration file in > /etc/systemd/system/ needs tweaking? My normal advice would be to talk to dnscrypt-proxy upstream or the supplier of your

Re: [systemd-devel] No rhyme or reason to systemd enabling/disabling service

On 29/07/16 18:56, Simon McVittie wrote: > So I'm not sure what you're doing, or > where your dnscrypt-proxy.{socket,service} came from. It's a bug in the Debian/Ubuntu packaging for dnscrypt-proxy, which have their own fork of the systemd units, possibly derived from 1.6.0. I've opened a bug in

Re: [systemd-devel] No rhyme or reason to systemd enabling/disabling service

On 07/29/2016 12:56 PM, Simon McVittie wrote: On 29/07/16 16:59, Chip wrote: On 07/29/2016 05:57 AM, Lennart Poettering wrote: My educated guess is that some cyclic dependency or so caused it to not be considered for activation at boot. Lennart's guess was correct: Jul 29 11:33:06

[systemd-devel] [ISSUE] network block when it kill teamd service with "Before=network-pre.target"

I want teamd.service is stopped after network is stopped when system shutdown, then I add two line in teamd.service as systemd-devel suggests. Before=network-pre.target Wants=network-pre.target But in /etc/sysconfig/network-scripts/ifdown-Team, it also kills teamd with: