Thanks. I realized that the service file depends on target file.
That "local-fs-pre.target" do nothing ? and then "local-fs.target" need
boot.mount first ? The boot.mount and the other mount they were executed
parallelize ?
And then arrived at "sysinit.target" , and then start some service
(console-setup.service,udevd.service, etc.) parallel ?
在 2015-10-26 16:42:03，"Mantas Mikulėnas" <[email protected]> 写道：
On Mon, Oct 26, 2015 at 10:13 AM, kennedy <[email protected]> wrote:
what's the relationship between the target file and the real executable file ?
"local-fs-pre.target" ,"local-fs.target" will start which service (will execute
which binary file) ?
None. They're .target units – their purpose is only to group other units. But
they don't necessarily depend on any .service unit at all – in fact with
local-fs*.target it's the opposite; *services* depend on these targets, and the
targets themselves only depend on mounts.
$ systemctl list-dependencies local-fs.target
local-fs.target
● ├─boot.mount
● ├─home.mount
● ├─tmp.mount
● └─var-lib-machines.mount
--
Mantas Mikulėnas <[email protected]>
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
