Killing paramters: status

[Jeremy Allison]

On Sun, Nov 11, 2001 at 08:44:18PM +1100, Andrew Bartlett wrote:
> Can anybody give me a good reason to run 'status = no'.
> 
> Apart from providing a minuscule performance gain and breaking plenty of
> things (yes, I think status = no is probably buggy), is there a reason
> for this parameter not to die (i.e. always status = yes)?

It was already removed in 2.2 I think. We do need a parameter
"deny modes = yes/no" to have the same effect (due to complaints
after removing status in 2.2). This is one of the reasons I'm
sensitive about removing parameters.

Jeremy.