Bug 633287
| Summary: | RFE: additional systemctl command line parameters | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jóhann B. Guðmundsson <johannbg> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | johannbg, lpoetter, metherid, mschmidt, notting, plautrba |
| Target Milestone: | --- | Keywords: | Triaged |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-07-26 01:07:09 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 784611 | ||
|
Description
Jóhann B. Guðmundsson
2010-09-13 13:53:43 UTC
I think the '-t service' might not be an obvious change here. For example, you may want active/failed sockets as well. Hum I'm not following you here Running systemctl list-units -t service (or systemctl list-units --type=service ) Will show you active and failed by default as things are now. What I'm suggesting is that you can list by "status" instead of having to resort to '| grep/awk/sed' fu magic For example if I want to know all failed service I simply pass systemctl list-units -t service --failed OK. Your first comment wasn't clear - from the wording it looked like you were suggesting that --active *implied* -t service. Moving systemd bugs to f15, since the systemd feature got delayed. --failed is supported now. The other three not yet. This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. It probably would be a good idea to add to that list --enabled, --disabled as well to replace the chkconfig --list which would list the unit along with the target it's enabled in. Something like... systemctl list-units -t service --enabled UNIT STATE TARGET DESCRIPTION dbus.service Enabled multi-user.target D-Bus System Message Bus display-manager.service Enabled graphical.target Display Manager etc... And to list services enabled in specific target it would be systemctl list-units -t service --enabled multi-user.target UNIT STATE TARGET DESCRIPTION dbus.service Enabled multi-user.target $DESC plymouth-quit.service Enabled multi-user.target $DESC plymouth-quit-wait.service Enabled multi-user.target $DESC rc-local.service Enabled multi-user.target $DESC systemd-logind.service Enabled multi-user.target $DESC systemd-user-sessions.service Enabled multi-user.target $DESC I think the best way to map all of which get started in the boot process for users/admins is not using a an list like chkconfig did to but rather using a simple pstree like layout ( systemd-tree or systemctl --tree ) on which target get started and service and what else get started/run beneath them ( sockets,timer units, mount unit,path units etc...). I think doing so ( tree layout ) would be the quickest to be adopted and also help in eliminating the "run level" thinking people have. This is now available in 206 with the new --state= switch. |