How does this command:

# mount_nfs -dis -g 8 -I 512 -R 3 -r 512 -w 512 solomon:/var/spool/uucp 

not comply with the resulting usage complaint?

usage: mount_nfs [-234bcdiLlNPsTU] [-a maxreadahead] [-D deadthresh]
                 [-g maxgroups] [-I readdirsize] [-o options] [-R retrycnt]
                 [-r readsize] [-t timeout] [-w writesize] [-x retrans]
                 rhost:path node

And yes, I really do want to set the read, write, and readdir sizes
to 512 bytes (to get around a network packet-size problem to which
I can find no other solution).  The server is up:

# ping solomon
PING solomon ( 56 data bytes
64 bytes from icmp_seq=0 ttl=255 time=2.807 ms
64 bytes from icmp_seq=1 ttl=255 time=2.755 ms
64 bytes from icmp_seq=2 ttl=255 time=2.555 ms
--- solomon ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.555/2.706/2.807/0.109 ms

and the mount point does exist:

# ls -ld /solomon/uucp
drwxr-xr-x  2 root  wheel  512 Jul  4 18:34 /solomon/uucp

# uname -a
FreeBSD fbsd70.uucp 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 
2008     [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

I get the same behavior, with a very slightly different usage
message, from a 6.1 system.  The server is an ancient sun3
running SunOS 4.1.1-U1, but it looks as if the mount attempt
is not getting far enough for that to matter.
_______________________________________________ mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to