From: "Paul D. DeRocco" <pderocco@ix.netcom.com>
To: <yocto@yoctoproject.org>
Subject: systemd configuration
Date: Tue, 2 Jul 2013 10:40:06 -0700 [thread overview]
Message-ID: <7AFA3235764547DFB27795FD58368F44@PAULD> (raw)
I've switched to systemd, in a core-image-base build for an Atom
(Cedartrail), and it boots fine. Now I want to make my own daemon start up.
I'm new to systemd, and the way it seems to be set up is different from the
way the systemd docs say it is usually set up.
The docs say that systemd, when booting up, usually activates a target
called default.target, which is symlinked to either multi-user.target or
graphical.target. (It would be the former in this GUI-less system.) Then, if
I want to cause my daemon to be started, I would add a symlink to its
systemd unit file to the .wants directory associated with multi-user.target.
But I can't find these things. They're not in the trees under /etc/systemd
or /run/systemd. Oh, and when I do "systemctl list-unit-files", it shows
both default.target and multi-user.target as disabled.
What makes this difficult to figure out is that the tools I have for
perusing the target system are so primitive. There's no editor in the target
that I'm aware of, and I can't network into the system and use an external
editor to examine various files. So my question is this: is there someplace
in build/tmp on my build system where the full target file system exists as
a directory tree, so that I can pore through it and see how systemd is
really configured?
Or perhaps someone can just tell me what target gets activated on bootup,
where its .wants directory is, and what directory I should put my daemon's
unit file into.
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com
next reply other threads:[~2013-07-02 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 17:40 Paul D. DeRocco [this message]
2013-07-02 22:17 ` systemd configuration Paul Eggleton
2013-07-03 8:30 ` Paul D. DeRocco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7AFA3235764547DFB27795FD58368F44@PAULD \
--to=pderocco@ix.netcom.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.