@kozaki
The man page has been updated. The omitted-fields example appears after the first example. I hope it will be clear now. Thanks for the feedback.
Search Criteria
Package Details: autochown 2015-1
Package Actions
| Package Base: | autochown |
|---|---|
| Description: | Monitor multiple directories using glob patterns and automatically adjust file ownership and permissions. |
| Upstream URL: | http://xyne.archlinux.ca/projects/autochown |
| Category: | system |
| Licenses: | |
| Submitter: | Xyne |
| Maintainer: | Xyne |
| Last Packager: | Xyne |
| Votes: | 4 |
| First Submitted: | 2012-09-17 05:04 |
| Last Updated: | 2015-01-27 09:50 |
Latest Comments
Comment by Xyne
Comment by kozaki
@Xyne thank you :)
Now I read you, it makes sense.
Man page could include an example, just to make sure. ie:
---
= INPUT FILE
= Lines the begin with "> " indicate target directories. They have the following format:
=
= > <user>:<group>:<mask>:<glob pattern>
=
= <user>, <group> and <mask> are all optional.
+ But you must leave the colon delimiters, e.g. to only change the owner:
+ nobody:::/path/to/dir
Comment by Xyne
@kozaki
The line without the mask should be
> user:group::/home/user/directory
Note the double colon after group. You may omit the user, the group or the mask, but you must leave the colon delimiters, e.g. to only change the owner:
> nobody:::/path/to/dir
Comment by kozaki
Immediately before as well as after updating to autochown-2014-2, a line _without a mask_ causes the following error:
---
Process: 10504 ExecStart=/usr/bin/autochown /etc/autochownd.conf (code=exited, status=1/FAILURE)
---
Line in fault:
> user:group:/home/user/directory
Causes the erreur above.
> user:group:007:/home/user/directory
Runs fine. Same with a mask of '113D002'.
Comment by Xyne
There was a bug in the 2013 releases prior to 2013.2.13.1. If you are using using one of them, please update immediately. The bug would follow symlinks outside of the target directory and could do some damage depending on what was symlinked.
Comment by Xyne
It should just need a unit file. I will write unit files for all of my packages as soon as I switch to systemd. I've been meaning to do it for weeks now, but things keep coming up and my time is limited.
Comment by zoqaeski
This could be really useful. Would it need any modifications to make it systemd-compatible? I'm reading the systemd manpages now to see if I can write a unit file for it, as I think that's all that's needed.