|
Bugzilla – Full Text Bug Listing |
| Summary: | systemd should tell me I'm stopping an unknown service | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.1 | Reporter: | Jiri Slaby <jslaby> |
| Component: | Basesystem | Assignee: | Frederic Crozat <fcrozat> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | crrodriguez |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
not sure if it is wanted or not.. Better to ask upstream for this.. (In reply to comment #1) > not sure if it is wanted or not.. Better to ask upstream for this.. Any replies on that site? Thanks. got upstream response : <fcrozat> mezcalero: quick question (for bnc#725481) : is it normal/wanted systemctl stop foobar.service (where foobar.service doesn't exist) doesn't output any error message (nor error code) ? <mezcalero> fcrozat: yupp systemd now needs to continue to keep track of the services' processes but it's a service with no unit file and the user should still be able to shut it down so in that case we need to make sure that units which failed to load still work fine with "stop" <fcrozat> it just makes live harder if you do a typo :) (which was the point of the bug in the first place ;) <mezcalero> well, i am pretty sure people would be more pissed off if systemd would fail stopping services that have no unit file closing as invalid, per upstream response |
Like start or status: # systemctl start franta.service Failed to issue method call: Unit franta.service failed to load: No such file or directory. See system logs and 'systemctl status franta.service' for details. # systemctl status franta.service franta.service Loaded: error (Reason: No such file or directory) Active: inactive (dead) With stop, there is no output: # systemctl stop franta.service # This is confusing when one does a typo...