Open alunduil opened 6 years ago
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
Issue description
When starting fcron on a freshly created host (via nixops), the service fails to start with an error indicating that
/var/spool/fcron
is not accessible (show below).Steps to reproduce
Enable fcron in a fresh configuration on nixops with VirtualBox (I have not verified this behavior without nixops). The host will be created and started correctly but the fcron service will fail to start.
I've tracked this to the permissions on
/var/spool
being 700 rather than 755. I believe a simple fix would be to change these permissions alongside the install of the/var/spool/fcron
directory in the fcron unit file but wanted to see if there wasn't a better solution first.Is there a way to consistently ensure that the
/var/spool
directory has 755 permissions rather than (on the nixops VirtualBox machine anyway) 700? If not, I'll submit a pull request that adds the permission change but it doesn't feel like the best solution.Technical details
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the results.