| 1 |
Am 26.07.2014 04:47, schrieb walt: |
| 2 |
|
| 3 |
> So, why did the "broken" machine work normally for more than a year |
| 4 |
> without rpcbind until two days ago? (I suppose because nfs-utils was |
| 5 |
> updated to 1.3.0 ?) |
| 6 |
> |
| 7 |
> The real problem here is that I have no idea how NFS works, and each |
| 8 |
> new version is more complicated because the devs are solving problems |
| 9 |
> that I don't understand or even know about. |
| 10 |
|
| 11 |
I double your search for understanding ... my various efforts to set up |
| 12 |
NFSv4 for sharing stuff in my LAN also lead to unstable behavior and |
| 13 |
frustration. |
| 14 |
|
| 15 |
Only last week I re-attacked this topic as I start using puppet here to |
| 16 |
manage my systems ... and one part of this might be sharing /usr/portage |
| 17 |
via NFSv4. One client host mounts it without a problem, the thinkpads |
| 18 |
don't do so ... just another example ;-) |
| 19 |
|
| 20 |
Additional in my context: using systemd ... so there are other |
| 21 |
(different?) dependencies at work and services started. |
| 22 |
|
| 23 |
I'd be happy to get that working in a reliable way. I don't remember |
| 24 |
unstable behavior with NFS (v2 back then?) when we used it at a company |
| 25 |
I worked for in the 90s. |
| 26 |
|
| 27 |
Stefan |
Archives