On 4/21/2013 12:29 PM, Marc Chamberlin wrote:
I have a funny quirk going on with apache2.service in openSuSE12.3 x64 and this behavior is different from other services.
If I stop the apache2.service -
systemctl stop apache2.service
then systemctl seems to lose almost all its understanding of the apache2.service. For example, if I issue this command -
systemctl --all --type=service
to determine the status of my services, the apache2.service is no longer shown in the output listing. Nor does auto complete for the service name work when I try to start it -
systemctl start apac(tab)
but if I type in the complete command as follows -
systemctl start apache2.service
that works! AND
systemctl --all --type=service
shows the apache2.service status AND I can now use auto complete to stop the service -
systemctl stop apa(tab) will auto complete this to systemctl stop apache2.service
WEIRD!! What gives? Is there something special about apache2.service that is goofing up systemctl? None of the other services behave like this, so far as I can tell....
Marc...
It gets worse... The systemd System Manager doesn't seem to know a thing about apache2.service, no matter what state it is in! Bug? Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org