But lockd was automatically started before when it was needed by either client
or server code. Why change it so the user can now forget to start it?
Especially in the stable kernel - I can appreciate the reasons for doing it in
the long term (2.3), but shouldn't we give a little more priority to
consistency?
How about incorporating this into 2.3, but leaving it out of 2.2?
Or perhaps an alternative would be to call the lockd() routine from statd - at
least that way the user doesn't have to start a new daemon which arrived late
in the 2.2 kernel.
---- ---- ----
David Woodhouse David.Woodhouse@mvhi.com Office: (+44) 1223 810302
Project Leader, Process Information Systems Mobile: (+44) 976 658355
Axiom (Cambridge) Ltd., Swaffham Bulbeck, Cambridge, CB5 0NA, UK.
finger dwmw2@ferret.lmh.ox.ac.uk for PGP key.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/