| 1 |
I've checked 1.1.4 & 1.2.2. Both don't seem to satisfy such a dependency: |
| 2 |
|
| 3 |
amit0 ~ # qlist -Iv nfs-utils |
| 4 |
net-fs/nfs-utils-1.1.4-r1 |
| 5 |
amit0 ~ # /etc/init.d/nfsmount ineed |
| 6 |
net rpcbind rpc.statd |
| 7 |
|
| 8 |
amit0 ~ # emerge -qKa nfs-utils |
| 9 |
[binary U ] net-fs/nfs-utils-1.2.2-r1 [1.1.4-r1] |
| 10 |
|
| 11 |
Would you like to merge these packages? [Yes/No] y |
| 12 |
>>> Emerging binary (1 of 1) net-fs/nfs-utils-1.2.2-r1 |
| 13 |
>>> Installing (1 of 1) net-fs/nfs-utils-1.2.2-r1 |
| 14 |
* GNU info directory index is up-to-date. |
| 15 |
|
| 16 |
* IMPORTANT: 1 config files in '/etc' need updating. |
| 17 |
* See the CONFIGURATION FILES section of the emerge |
| 18 |
* man page to learn how to update config files. |
| 19 |
amit0 ~ # /etc/init.d/nfsmount ineed |
| 20 |
* Caching service dependencies |
| 21 |
... |
| 22 |
[ ok ] |
| 23 |
net rpcbind rpc.statd |
| 24 |
amit0 ~ # etc-update |
| 25 |
Scanning Configuration files... |
| 26 |
The following is the list of files which need updating, each |
| 27 |
configuration file is followed by a list of possible replacement files. |
| 28 |
1) /etc/conf.d/nfs (1) |
| 29 |
Please select a file to edit by entering the corresponding number. |
| 30 |
(don't use -3, -5, -7 or -9 if you're unsure what to do) |
| 31 |
(-1 to exit) (-3 to auto merge all remaining files) |
| 32 |
(-5 to auto-merge AND not use 'mv -i') |
| 33 |
(-7 to discard all updates) |
| 34 |
(-9 to discard all updates AND not use 'rm |
| 35 |
-i'): 1 |
| 36 |
|
| 37 |
File: /etc/conf.d/._cfg0000_nfs |
| 38 |
1) Replace original with update |
| 39 |
2) Delete update, keeping original as is |
| 40 |
3) Interactively merge original with update |
| 41 |
4) Show differences again |
| 42 |
Please select from the menu above (-1 to ignore this update): 1 |
| 43 |
Replacing /etc/conf.d/nfs with /etc/conf.d/._cfg0000_nfs |
| 44 |
mv: overwrite `/etc/conf.d/nfs'? y |
| 45 |
|
| 46 |
Exiting: Nothing left to do; exiting. :) |
| 47 |
amit0 ~ # /etc/init.d/nfsmount ineed |
| 48 |
* Caching service dependencies |
| 49 |
... |
| 50 |
[ ok ] |
| 51 |
net rpcbind rpc.statd |
| 52 |
amit0 ~ # /etc/init.d/rpc.idmapd status |
| 53 |
* status: stopped |
| 54 |
amit0 ~ # /etc/init.d/nfsmount start |
| 55 |
* Starting NFS sm-notify |
| 56 |
... |
| 57 |
[ ok ] |
| 58 |
* Mounting NFS filesystems |
| 59 |
... |
| 60 |
[ ok ] |
| 61 |
amit0 ~ # /etc/init.d/rpc.idmapd status |
| 62 |
* status: stopped |
| 63 |
|
| 64 |
Could you therefore clarify? |
| 65 |
Amit |
| 66 |
|
| 67 |
|
| 68 |
On 06/14/10 21:13, Mike Frysinger wrote: |
| 69 |
> On Mon, Jun 14, 2010 at 2:43 AM, Amit Dor-Shifer wrote: |
| 70 |
> |
| 71 |
>> I read in idmapd's manpage that "It provides functionality to the NFSv4 |
| 72 |
>> kernel client and server". I'm therefore wondering whether it'd be desired |
| 73 |
>> to facilitate an rc dependency of nfsmount (client-side) in rpc.idmapd. |
| 74 |
>> /etc/init.d/nfs (server side) allows that via NFS_NEEDED_SERVICES. |
| 75 |
>> |
| 76 |
> nfsmount already depends on rpc.idmapd when necessary |
| 77 |
> -mike |
| 78 |
> |
| 79 |
> |
Archives