I love systemd and journal, but resolved is just broken. Especially since you can enable dnsmasq in NetworkManager and solve the same issue with something really well tested.
I’m fascinated by the way they added the test case to the make file. I’m not much of a C person so my question is: is this a common convention since there is no auto discovery of tests?
It’s relatively common in C, but I personally can’t stand it, since it puts a high barrier on adding new tests (automating things shouldn’t be inconvenient!). This is one of the reasons I like gtest for C/C++ applications (https://github.com/google/googletest).
I know that the systemd hate is strong here, but this was already posted a couple of days ago:
https://lobste.rs/s/lockbb/usn_3341_1_systemd_vulnerability
I was worried that there was yet another vulnerability in systemd-resolved ;).
Yeah, you should flag it as ‘already posted’ I think
cough NIH.
This.
I love
systemdandjournal, butresolvedis just broken. Especially since you can enablednsmasqin NetworkManager and solve the same issue with something really well tested.I’m fascinated by the way they added the test case to the make file. I’m not much of a C person so my question is: is this a common convention since there is no auto discovery of tests?
For library code, generally. You need to write a little program that calls the function you want to test.
It’s relatively common in C, but I personally can’t stand it, since it puts a high barrier on adding new tests (automating things shouldn’t be inconvenient!). This is one of the reasons I like gtest for C/C++ applications (https://github.com/google/googletest).