Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#29217 - [darkstat] specify an existing home directory or cron will complain
Attached to Project:
Community Packages
Opened by Clemens Buchacher (drizzd) - Sunday, 01 April 2012, 10:35 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 10 April 2012, 03:36 GMT
Opened by Clemens Buchacher (drizzd) - Sunday, 01 April 2012, 10:35 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 10 April 2012, 03:36 GMT
|
DetailsDescription:
The darkstat installation script adds a new user "darkstat", but it does not specify a home directory. This triggers a sanity check in cron.daily. It gives the following error: user 'darkstat': directory '/home/darkstat' does not exist pwck: no changes The attached patch fixes the issue by pointing the darkstat user's home directory to the existing chroot for darkstat. Additional info: community/darkstat 3.0.715-1 Steps to reproduce: 1. Add darkstat to DAEMONS in /etc/rc.conf. 2. Wait one day. 3. Check root mailbox for messages from cron. |
This task depends upon
Closed by Sergej Pupykin (sergej)
Tuesday, 10 April 2012, 03:36 GMT
Reason for closing: Fixed
Additional comments about closing: thanks
Tuesday, 10 April 2012, 03:36 GMT
Reason for closing: Fixed
Additional comments about closing: thanks
0001-specify-an-existing-home...