| Summary: | openafs init script error | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | M Grundman <grundman> |
| Component: | Current packages | Assignee: | Stefaan De Roeck (RETIRED) <stefaan> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | net-fs, rutledad |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
M Grundman
2004-03-22 05:43:28 UTC
OpenAFS needs a developer to take up maintenance. I'm not sure killing afsd is the correct way. Although afsd appears as a process, it is a kernel process and the only correct way I believe available to shut it down - and get /afs unmounted - is to use "afsd -shutdown". Unfortunately, that never worked for me on linux. New ebuilds for openafs 1.2.13 (stable) and 1.3.85 (experimental) are available for testing. According to openafs-ml, 1.3.85 is currently undergoing testing so it can become 1.4rc. The scripts haven't been modified to forcefully kill any process still using the /afs mount, seems a bit harsh. But I haven't had any problems with cleanly unmounting /afs lately (I mostly use 1.3.85, but I've tested 1.2.13 for a short while as well). It'd be great if these new proposed ebuilds could be tested, to see if the problem remains The init script has been modified to shutdown the afs client parts in the correct order. The main reason was probably the openafs-package itself, as I got the same errors a few versions ago when shutting down correctly. It seems to work correctly now though. I'm therefore assuming this to be fixed. |