My particular use case is launching user specific vncserver instances with @reboot. Service launches fail because the binding interface isn't initialized when cron daemon starts. Yes I can make systemd units for my services, but I think there's still an issue here. Similar discussion https://bugzilla.redhat.com/show_bug.cgi?id=747759 Reproducible: Always
Upstream is Fedora. Their solution to the referenced Red Hat bug was to make cronie start after sssd.service and ypbind.service to prevent NSS lookup failures. http://pkgs.fedoraproject.org/cgit/cronie.git/commit/cronie.systemd?id=00f22a545119a93f54b0257d71d0b98ecb1407b2 That issue is a bit different from your issue, where you are actually starting a network daemon (vncserver) from a cron job. I don't think it necessarily makes sense to have cron start after network.target for all Gentoo users. I think it is quite rare that an @reboot job would require network access. If you need it for your use case, you can override the unit like this: $ cat /etc/systemd/system/cronie.service.d/network.conf [Unit] After=network.service
Learning about section level overrides in systemd was worth filing the bug. Thanks.
Oops; I mixed up .service and .target in my head. That should read: [Unit] After=network.target
