| Summary: | /var/lib/rpcbind not created during package install | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bit Twister <bittwister2> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, smelror |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | rpcbind-0.2.4-1.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Bit Twister
2018-02-14 12:54:15 CET
Assigning to all packagers collectively, since there is no registered maintainer for this package. Assignee:
bugsquad =>
pkg-bugs The rpcbind package in Mageia used to use /var/lib/rpcbind as the statedir (--with-statedir option to configure), but no longer does. Now it uses /run/rpcbind. /var/lib/rpcbind is still set as the home directory of the rpc user, but as it's a system user, it shouldn't matter that the directory doesn't exist. Funny enough the SPEC still creates /var/lib/rpcbind in %install, but no longer packages it. I suppose the home directory of the rpc user could be changed to /run/rpcbind, but it probably doesn't matter either way. (In reply to David Walser from comment #2) > Now it uses /run/rpcbind. /var/lib/rpcbind is still set as the home > directory of the rpc user, but as it's a system user, it shouldn't > matter that the directory doesn't exist. I agree operationally is not affected, but why not set /run/rpcbind in the rpc user creation entry into passwd. Or post-install command to create /var/lib/rpcbind. As a system admain, I would prefer a clean result from pwck -r and grpck -r on a clean install. (In reply to Bit Twister from comment #3) > (In reply to David Walser from comment #2) > > Now it uses /run/rpcbind. /var/lib/rpcbind is still set as the home > > directory of the rpc user, but as it's a system user, it shouldn't > > matter that the directory doesn't exist. > > I agree operationally is not affected, but why not set /run/rpcbind in the > rpc user creation entry into passwd. > Or post-install command to create /var/lib/rpcbind. > > As a system admain, I would prefer a clean result from pwck -r and grpck -r > on a clean install. Thomas gave me an explanation on why we should not create stuff in /run. https://bugs.mageia.org/show_bug.cgi?id=22574#c10 CC:
(none) =>
smelror |