@ndowens, thanks for your PR! By analyzing the history of the files in this pull request, we identified @domenkozar, @edolstra and @MarcWeber to be potential reviewers.

I removed:
"--with-username=root"
"--with-groupname=root"
Because fcron will no longer build using root as a user

services.fcron.enable = true;

The module fails to start on my system (stops with 0 after being started)

Mar 02 10:37:31 turingmachine systemd[1]: Starting fcron daemon...
Mar 02 10:37:31 turingmachine fcron-pre-start[9395]: 2017-03-02 10:37:31 ERROR user "fcron" is not in passwd file. Aborting.: Success
Mar 02 10:37:31 turingmachine fcron-pre-start[9395]: 2017-03-02 10:37:31 ERROR fcron child aborted: this does not affect the main fcron daemon, but
Mar 02 10:37:31 turingmachine systemd[1]: Started fcron daemon.

Hmm have to look at the module I guess. Because I had to remove root, wonder if hat caused the error

@ndowens the modules needs to add a fcron user I guess.

@Mic92 #23413 fixes this

@ndowens not really, Please test if your changes actually work before opening pull requests

@Mic92 I did; I used build-vm; the first time I seen error in the log by journalctl and then I updated the module, by adding fcron user and I seen no error in the journal and it seemed as fcron was running when I looked at ps -a

/var/spool/fcron was not owned by the fcron users for instance. So adding new crontabs would not have worked.

Sorry, I thought it worked, I tested it as much I understood it; I never really experienced cron jobs or anything; so I have very limited experience in that area. I just knew that before I added the user, journal had red error for it, and after I added user I didnt see any error; so thought it was fixed