Since I don't have internet access on the machine with the problem, there is a chance some of the problems (shorewall mainly) may be due to that. The others don't seem to be getting at all their onfiguration files. (For apache, /etc/conf.d/apache2, and for mysql, /etc/mysql/my.cnf.) Below are results from running systemctl status <name>

Note that apache2 has configuration information for fastcgi, and mysqld has the wrong data directory which is defined in /etc/mysql/my.cnf. So how does systemd get the correct configuration information? Thanks,
Fred

You should check if the systemd unit files are present for these packages. If not, re-emerge them. I didn't look into your error messages, and I don't use systemd myself, so I might be wrong, but I understand the unit files where introduced without version bump and those three packages might have been emerged last time well before that._________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

Thanks for the info. If I don't have unit files for apache and mysql I can't run with systemd. The problems I'm having with mysqld might be solved with some softlinks although so far that has not got it working. It would have been nice if this sort of issue had been publicized in a more visible way.

Well, using ~arch packages there is no guarantee of any notification or finished documentation about imminent breakage. This is one of those occasions. _________________backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic

I posted another message here by mistake. I finally have an internet with my main computer. I'm not quite ready to give up on systemd, but I'm close. I can't go further without a firewall (hence this is being posted from a second machine a pitiful laptop). systemctl status shorewall is still giving me what I posted above. If I can get that working, I'll try to work on the others.[/quote]

Internet works on about 1 in 5 reboots. I'm giving up on sysstemd. It seems even if I get it to boot reliably which I don't know how to do) there are too many other things that are likely to lead to failure.

i purged my systemd, it was great while it lasted. im scared of removing udev and having systemd take over udev responsibilities and keeping openrc going. i require the option to switch between the two so i can run with systemd for fun, and when i need to be serious boot openrc.

I have systemd booting just fine with persistent names. But still no networking if I use persistent names with openrc. I have not tried systemd since installing a couple of updates to systemd, but I know of no reason to think that the changes will make shorewall, apache, mysql, etc. work.

I found solution with systemd-love Portage overlay(https://github.com/Sabayon/systemd-love), that allow to start current GNOME 3.8 on openrc. But I does not test it.
I do not want to switch to gnome 3.6 and systemd does not want to work with mysql. What do you do?!?!

I was wrong.Sabayon is modern and easy to use Linux distribution based on Gentoo. It is not solution.

snum wrote:

I found solution with systemd-love Portage overlay(https://github.com/Sabayon/systemd-love), that allow to start current GNOME 3.8 on openrc. But I does not test it.
I do not want to switch to gnome 3.6 and systemd does not want to work with mysql. What do you do?!?!

Using the mysqld.service file available from portage, systemctl reports mysql as having started. However I can't enter mysql as it "can't find /var/run/mysqld/mysql.sock".

It seem as if systemd does not refer to /etc/mysql/my.cnf. The socket seems always to have been created automatically under the previous init.d system.

I'm using mysql for mythtv and hoping to continue with the current database, so if anyone can tell me how to get systemd to create the necessary socket etc., I'd be most grateful.
*********************************************
I noted after writing the above that danielLTU's script, above, executes mysqld from /usr/sbin/ and not /usr/bin/ as the portage script does. I have copied and tried his/her script with the same result; it completes, but still wants for /var/run/mysqld/mysqld.sock. I noted that /var/run/ is a simlink to /run so I created a directory "mysqld" under /run but that had no effect.

**********LATER***************
Looked at the original web page for the above service file, and noted the need for tempory file creation below beneath it. Copied this and it did the trick.

However it seems my mythtv database is no longer compatible with the "updated" mysql, so I must now attempt to sort that one out!!