On 08/20/2011 08:09 AM, Lars Seipel wrote:
On Sat, 2011-08-20 at 00:13 +0200, Reindl Harald wrote:
if you can give a warning you can also stop the socket
this is what the user expects and if your software-design
is not able to act logically it is broken
Stopping the service but leaving the possibility for later socket
activation is a valid use case. Warning about that because it also could
be a mistake is a nice service and sufficient.
How can you say that? I stopped the serivce! I don't expect it to magically
start backup!!!
You are just plain wrong. Any system should be about doing things with the "least
surprise to the user"!
"service restart htt"
you can type TAb the whole day and will get no auto-completion
Of course not. This is wrong syntax.
systemctl restart htt<tab>
should do what you're trying to accomplish. If you insist on using the
"service" wrapper script, the appropriate syntax would be:
service htt<tab> restart
It does fine in both cases.
yes it is a improvent to get htis after the boot but if you restart a server
you nromally watch the boot and have no reason to login as long you see
nothing red - this was broken by the usability-pifall how systemd boots
I'm pretty certain that failures are colored red. Are you sure you got
your facts right?
Lars
--
Stephen Clark
*NetWolves*
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.cl...@netwolves.com
http://www.netwolves.com
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
