Comment # 10 on bug 969528 from Ren� Br�unling

(In reply to Stefan Schubert from comment #9)
> (In reply to Patrick Schaaf from comment #8)
> > 
> > As I wrote above, that chrome package contains a post install script that
> > insists on running some kind of "at" job, and to that end, nowadays contains
> > a call to start atd (the "systemctl start --full atd.service" we saw in the
> > process list) - and THAT is what is hanging, presumably because atd depends
> > on syslog.service, but syslog.service is not running in the autoyast
> > environment at that point in time.
> 
> Well, we are in the second stage of installation so we are already in the
> installed system. We have reduced the running services to a amount which we
> are really needed. Otherwise we have had a lot of cycle problems (as you
> have now)
> So you can try to add the service to the service section:
> 
>   <services-manager>
>     <default_target>graphical</default_target>
>     <services>
>       <disable config:type="list"/>
>       <enable config:type="list">
>         <service>rsyslog</service>
> 
> ...
> ..
> .
> or you can try to start it in your init script before starting the RPM
> installation:
> systemctl start syslog.service

Adding

systemctl start syslog.service

to the script does not work.
Log entry:

+ systemctl start syslog.service
Failed to start syslog.service: Unit syslog.service failed to load: No such
file or directory.