Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Anatomy of a DNS Lookup – Part II

zwischenzugs.com

Post reply on HN
Print view View original

1–10 of 10 posts

Re: Anatomy of a DNS Lookup – Part II

#3

Post by pmoriarty »

"The --read-environment flag is undocumented, and is there so that systemctl can play nice with it. A lot of people hate systemctl for this kind of thing."

Is such undocumented behavior an intentional, acknowledged policy of systemd?

Or is this just something that got overlooked and will/should be documented sometime?

Re: Anatomy of a DNS Lookup – Part II

#5

Post by gcommer »

pmoriarty wrote: post #3

"The --read-environment flag is undocumented, and is there so that systemctl can play nice with it. A lot of people hate systemctl for this kind of thing." Is such undocumented behavior an intentional, acknowledged policy of systemd? Or is this just something that got overlooked and will/should be documented sometime?

Its not a part of systemd, its a part of ifupdown that was added to aide Debian's transition from SysV to systemd. Seems unfair to me to count this against systemd; there are other less intrusive ways this could've been done, and "allow reading configuration from env vars" is probably a good thing anyways.

https://github.com/wido/ifupdown/commit/c29820f370a4905b8366...

Re: Anatomy of a DNS Lookup – Part II

#6

Post by riobard »

gcommer wrote: post #5
pmoriarty wrote: post #3

"The --read-environment flag is undocumented, and is there so that systemctl can play nice with it. A lot of people hate systemctl for this kind of thing." Is such undocumented behavior an intentional, acknowledged policy of systemd? Or is this just something that got overlooked and will/should be documented sometime?

Its not a part of systemd, its a part of ifupdown that was added to aide Debian's transition from SysV to systemd. Seems unfair to me to count this against systemd; there are other less intrusive ways this could've been done, and "allow reading configuration from env vars" is probably a good thing anyways. https://github.com/wido/ifupdown/commit/c29820f370a4905b8366...

Is there any detailed roadmap of Debian's transition from SysV to systemd? Currently it's a mess in Debian 9 where some packages come with traditional init scripts and some with systemd unit files, and some even with upstart scripts.

Re: Anatomy of a DNS Lookup – Part II

#7

Post by zwischenzug »

gcommer wrote: post #5
pmoriarty wrote: post #3

"The --read-environment flag is undocumented, and is there so that systemctl can play nice with it. A lot of people hate systemctl for this kind of thing." Is such undocumented behavior an intentional, acknowledged policy of systemd? Or is this just something that got overlooked and will/should be documented sometime?

Its not a part of systemd, its a part of ifupdown that was added to aide Debian's transition from SysV to systemd. Seems unfair to me to count this against systemd; there are other less intrusive ways this could've been done, and "allow reading configuration from env vars" is probably a good thing anyways. https://github.com/wido/ifupdown/commit/c29820f370a4905b8366...

Author here.

It may be unfair, I didn't mean to imply any kind of judgement. 'This kind of thing' was vague, but was intended to get over the fact that systemd is taking over more and more of the OS, and people don't like this. Whether this is good or bad I'm fairly agnostic on. At least it's managed and a standard.

Re: Anatomy of a DNS Lookup – Part II

#9

Post by aargh_aargh »

zwischenzug wrote: post #7
gcommer wrote: post #5

Earlier quoted context omitted.

Its not a part of systemd, its a part of ifupdown that was added to aide Debian's transition from SysV to systemd. Seems unfair to me to count this against systemd; there are other less intrusive ways this could've been done, and "allow reading configuration from env vars" is probably a good thing anyways. https://github.com/wido/ifupdown/commit/c29820f370a4905b8366...

Author here. It may be unfair, I didn't mean to imply any kind of judgement. 'This kind of thing' was vague, but was intended to get over the fact that systemd is taking over more and more of the OS, and people don't like this. Whether this is good or bad I'm fairly agnostic on. At least it's managed and a standard.

I'm not one to flame on systemd but I have to correct you there - it's not a standard, it's a single implementation.
Post reply on HN