Mihai's questions

I've got the following minimal test case on Apache 2.4.6:

<VirtualHost *:80>
    # Match all paths excluding /proxy
    <LocationMatch ^/prefix/((?!proxy/).*)$>
        ProxyPassMatch http://127.0.0.1:8082/$1
    </LocationMatch>

    # Match /proxy specifically
    <Location /prefix/proxy/>
        ProxyPass "http://127.0.0.1:8082/proxy/"
    </Location>
</VirtualHost>

(The two locations do the same thing here, but they'll be configured differently on a production machine, of course.)

When trying to run Apache with this config, it fails with the following error:

AH00526: Syntax error on line 7 of /etc/httpd/conf.d/broken.conf:
ProxyPass/<Proxy> and ProxyPassMatch/<ProxyMatch> can't be used altogether
  with the same worker name (http://127.0.0.1:8082/$1)

I can't figure out what the error message means (it's not even proper English!) and how to solve it. From what I see, the ProxyPass worker names are different - they must be different, since the URLs are mutually exclusive!

Google returns only 3 hits for the error, and two of them point to the Apache source code. If I remove either one of the directives on line 3 and line 7, the config works fine.

Let's say I want to tag a Docker image, and make a typo. How do I remove the tag without removing the image itself? Neither the manpages nor the Docker documentation mention removing tags.

docker tag 0e5574283393 my-imaj
docker tag 0e5574283393 my-image
# docker untag my-imaj # There is no "docker untag"!

If I add a new DNS server using nmcli connection modify eth0 +ipv4.dns 8.8.8.8, I still have to update /etc/resolv.conf for the resolver to pick up the changes, right? So how do I force the update?

The only way I found was restarting the network service: /etc/init.d/network restart. Is there a less invasive way -- a nmcli command, perhaps?

We have a fairly complex systemd service with Type=notify. Very occasionally, the service will hang on startup/restart, and enter the failed state after systemd failes to receive a sd_notify call. We would like to restart the service in these cases - chances are, the second time it will start correctly.

However, the systemd.service(5) manual page says:

When the death of the process is a result of systemd operation (e.g. service stop or restart), the service will not be restarted.

Is there a way to overcome this restriction in the systemd configuration? Otherwise we will have to monitor the daemon status and manually restart it everytime it's stuck, or develop some kind of supervisor script for this, which may introduce more failure points into the system.