On Tue, 24.08.10 12:31, Matthew Miller (mat...@mattdm.org) wrote:
As I was thinking about Bug 626840, I noticed something. With the current
runlevel system, it's easy to know what your options are. The systemd FAQ
helpfully explains that systemctl isolate graphical.target is the
replacement,
On Tue, Aug 24, 2010 at 10:57:38PM +0200, Lennart Poettering wrote:
Actually it only shows you the active targets, those which a pending
job, and those which have failed before (i.e. the interesting
ones). If you pass --all it will show you inactive targets without
pending jobs which haven't
On Tue, 24.08.10 17:13, Matthew Miller (mat...@mattdm.org) wrote:
On Tue, Aug 24, 2010 at 10:57:38PM +0200, Lennart Poettering wrote:
Actually it only shows you the active targets, those which a pending
job, and those which have failed before (i.e. the interesting
ones). If you pass
On Tue, Aug 24, 2010 at 11:49:56PM +0200, Lennart Poettering wrote:
Wait, so --all doesn't actually show me all targets, it shows me an
apparently-arbitrary list of some of the possible targets?
It shows you all targets systemd knows about at that point in time.
The list of thinkable targets
On Tue, 24.08.10 18:07, Matthew Miller (mat...@mattdm.org) wrote:
On Tue, Aug 24, 2010 at 11:49:56PM +0200, Lennart Poettering wrote:
Wait, so --all doesn't actually show me all targets, it shows me an
apparently-arbitrary list of some of the possible targets?
It shows you all targets
On Wed, Aug 25, 2010 at 12:36:54AM +0200, Lennart Poettering wrote:
$ systemd --test --system --unit=foobar.target
This will dump you a lot of stuff, including, at the very end the
transaction it would execute when it would be booted with this target as
destination.
This is mostly a
