Frank Filz

With no action on this in nearly 30 days, I am going to close this as resolved. Please re-open if it is still an issue on a currently supported version...

I will be merging this patch this week. @koen-struyve-q if you could add a review comment and a verify +1 to the gerrithub patch that would be nice, but not...

named_attr is one that probably should be removed...

So what was the actual error? I would consider an option to force exit on any config failure during startup, but as Daniel says, many users of Ganesha depend on...

Another problem that was observed with problem exports in clustered environments is the cluster software restarting Ganesha and then Ganesha bouncing up and down as it is continuously restarted with...

What I meant was what is actually wrong with the config file? That will help me determine how best to address where the error should be handled.

It would be nice if the parser spit out more information about an error... It would be nice if someone a bit more familiar with Bison and Lex could dig...

Could you try with Ganesha V4.0.3? V2.8.4 is very old.

Closing this due to age, feel free to re-open if it's still of interest and you have explored using a currently supported version of Ganesha (V2.8 or V3 at this...

Hmm, it's possible the PrincipleName has to be "[email protected]" that seems to be the format the function call the principle name is used in is expecting.