Skip to contentSkip to conversation

pynfs and server attributes?

DISCUSSION Jeff Garzik 2 participants 3 messages Dec 10, 2007

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Is there a pynfs list somewhere?

The pynfs tests for too-long strings, too-long reads and writes do not seem to take into account maxname, maxread and maxwrite attributes.

I actually have to _increase_ the python "longname" test variable in order for the test to behave properly on my server :)

Jeff

P.S. Thanks to all who contributed to pynfs, it's been a great help.

#1 lore raw
Quoted 2 lines · Jeff Garzik

Is there a pynfs list somewhere?

Not that I know of.

Quoted 5 lines

The pynfs tests for too-long strings, too-long reads and writes do not seem to take into account maxname, maxread and maxwrite attributes.

I actually have to _increase_ the python "longname" test variable in order for the test to behave properly on my server :)

Jeff

The fixed (but easily changeable) "longname" was intentional in order to avoid test dependencies on GETATTR, and non-mandatory attributes at that.

Would making the length of longname a command line option be useful?

Quoted 5 lines

P.S. Thanks to all who contributed to pynfs, it's been a great help.

I'm glad it is useful.

Fred

#2 lore raw
Quoted 10 lines · Fredric Isaman
Quoted 2 lines · Jeff Garzik

Is there a pynfs list somewhere?

Not that I know of.

Quoted 2 lines

The pynfs tests for too-long strings, too-long reads and writes do not seem to take into account maxname, maxread and maxwrite attributes.

Quoted 8 lines
Quoted 3 lines

I actually have to _increase_ the python "longname" test variable in order for the test to behave properly on my server :)

Jeff

The fixed (but easily changeable) "longname" was intentional in order to avoid test dependencies on GETATTR, and non-mandatory attributes at that.

Would making the length of longname a command line option be useful?

Definitely. That, and the max-read and max-write attributes.

There is at least one test that issues a WARNING when my server returns 128k (its max read size) rather than the requested 9000000 count.

I have not investigated that yet, but I was sorta assuming that my server was behaving correctly in that case.

Jeff