1 |
On 8/3/19 2:43 PM, Ralph Seichter wrote: |
2 |
> + |
3 |
> +EAPI=7 |
4 |
> + |
5 |
> +inherit acct-user |
6 |
> + |
7 |
> +ACCT_USER_ID=333 |
8 |
> +ACCT_USER_GROUPS=( amavis ) |
9 |
> +DESCRIPTION="User for mail-filter/amavisd-new" |
10 |
> + |
11 |
> +acct-user_add_deps |
12 |
|
13 |
The existing user created by the amavisd-new ebuilds has a home |
14 |
directory of /var/amavis. This was done to match the default value of |
15 |
$MYHOME in the upstream config file, but is wrong: the FHS says that |
16 |
applications should not create top-level directories in /var for their |
17 |
own use. The right place for amavis' data is under /var/lib/amavis. And |
18 |
now is certainly the time to make that change if we're ever going to |
19 |
make it. |
20 |
|
21 |
If we were to do so a month ago, we would have set the user's home |
22 |
directory to /dev/null and used keepdir on /var/lib/amavis, because |
23 |
otherwise the "home" directory itself would be left untracked by the |
24 |
package manager. However, the acct-user eclass is smart enough to |
25 |
keepdir the new home directory for us. That makes me think that we |
26 |
should set |
27 |
|
28 |
ACCT_USER_HOME=/var/lib/amavis |
29 |
|
30 |
to avoid the extra step. Does anyone see a downside to that, versus |
31 |
leaving the homedir at /dev/null and creating the "extra" directory |
32 |
under /var/lib? |