core: expose PrivateTmp=disconnected
authorMike Yuan <me@yhndnzj.com>
Tue, 18 Jun 2024 14:18:56 +0000 (16:18 +0200)
committerMike Yuan <me@yhndnzj.com>
Fri, 21 Jun 2024 15:31:44 +0000 (17:31 +0200)
commit9d50d053f327e5471a514bc36487bfc3358c15d8
treef464e0de7a484277351256c17c55d080266b7c4e
parentd7f24848baad5fe65564c473434902ba45aadda9
core: expose PrivateTmp=disconnected

As discussed in https://github.com/systemd/systemd/pull/32724#discussion_r1638963071

I don't find the opposite reasoning particularly convincing.
We have ProtectHome=tmpfs and friends, and those can be
pretty much trivially implemented through TemporaryFileSystem=
too. The new logic brings many benefits, and is completely generic,
hence I see no reason not to expose it. We can even get more tests
for the code path if we make it public.
man/org.freedesktop.systemd1.xml
man/systemd.exec.xml
src/core/dbus-execute.c
src/core/load-fragment-gperf.gperf.in
src/core/load-fragment.c
src/core/namespace.c