Alan Cox wrote:
>
> > the problem is that a "rpciod" kernel-thread references the initrd,
> > and so umounting and freeing it, isn't possible.
> >
> > has anybody an idea how to fix this problem, cause it would be nice,
> > to free the initrd ram on a diskless node.
>
> It shouldnt be keeping a reference. daemonize() should have dropped its
> resources
hmm, i've now created a /initrd directory to let the the change_root of
the
initrd work correctly.
and then i looked with fuser, what processes reference the initrd:
---
root@ws4:~ $ fuser -mv /initrd/
USER PID ACCESS COMMAND
/initrd/ root 67 .rc..
rpciod
---
only the rpciod references the initrd, none of the other
kernel-threads.
Regards,
Daniel
--
Daniel Wagner | mailto:daniel@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Aug 23 2001 - 21:00:22 EST