undefined | Better HN

0 pointsqbasic_forever3y ago0 comments

Do you have an example of when systemd is not used for good?

0 comments

It's quite annoying to not be able to use common tools for DNS queries like `dig`, when using `systemd-resolved` for DNS. I think you might have to sometimes flush the caching feature of `systemd-resolved` as well.

It's fine, I guess. But it did take a while to learn the new ways.

I think this is the main complaint from users with decades of experience. Their scripts and old knowledge stops working.

egberts13y ago

it kills production daemons having long running stateful data whenever the netdev goes offline., systemd-networkd, that is.

viraptor3y ago

Only if you configure it to do that. You can use Wants= and After= for your service to start it after the network, but not restart otherwise.

The behaviour you describe is not unreasonable to want: If your network device goes away, what exactly are you binding the socket to? How are you restoring the listening when it comes back up? But it's up to you to say which one you want.

egberts13y ago

Its never a good systemd-networkd default to be killing daemon whenever a netdev goes “cricket”.

1 more reply

j / k navigate · click thread line to collapse

0 comments

houzi3y ago

It's fine, I guess. But it did take a while to learn the new ways.

I think this is the main complaint from users with decades of experience. Their scripts and old knowledge stops working.

egberts13y ago

it kills production daemons having long running stateful data whenever the netdev goes offline., systemd-networkd, that is.

viraptor3y ago

Only if you configure it to do that. You can use Wants= and After= for your service to start it after the network, but not restart otherwise.

egberts13y ago

Its never a good systemd-networkd default to be killing daemon whenever a netdev goes “cricket”.

1 more reply

j / k navigate · click thread line to collapse