On Tue, 26 Jun 2012 15:35:44 +0200 686f6c6d <686f6c6d@googlemail.com> wrote:
On Tue, Jun 26, 2012 at 2:21 PM, Conny Seidel <conny.seidel@amd.com> wrote:
I'm having difficulties enabling systemd services in openSUSE 12.2 from the autoyast file. [...] At least not for rpcbind. My workaround currently is to use a post-script to do a "systemctl enable rpcbind.service".
"Have you tried turning it off and on again?"
Yes, but rpcbind isn't working even after an reboot so our systemd-service file to start testing, which relies on $remotefs, doesn't start and the machine just boots and does nothing.
Seriously, as described in the other thread, I'm seeing a similar problem on 12.*1* where systemd/systemctl does neither display correctly nor bring up the <runlevel>-defined services during first boot. When I use <general><mode> <final_reboot><config:type="boolean">true</final_reboot> </mode></general>, the services are correctly configured and running after the reboot.
I knew that. ;) But unfortunately it doesn't work. rpcbind seems to get enabled, but without enabling rpcbind.socket, which pretty much renders nfs-mounts useless without the "-o nolock" option. Our way with systemctl shows this in the logfile, we generate for each script we run within the install process: ln -s '/lib/systemd/system/rpcbind.service' \ '/etc/systemd/system/multi-user.target.wants/rpcbind.service' ln -s '/lib/systemd/system/rpcbind.socket' \ '/etc/systemd/system/sockets.target.wants/rpcbind.socket' -- Kind regards. Conny Seidel ################################################################## # Email : conny.seidel@amd.com GnuPG-Key : 0xA6AB055D # # Fingerprint: 17C4 5DB2 7C4C C1C7 1452 8148 F139 7C09 A6AB 055D # ################################################################## # Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach # # General Managers: Alberto Bozzo # # Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen # # HRB Nr. 43632 # ##################################################################