[root@darkstar tmp [j0]#>>> mount -v 192.168.16.71:/var/www/ /mnt/hd/
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Sat Dec 25 07:54:27 2010
mount.nfs: trying text-based options 'vers=4,addr=192.168.16.71,clientaddr=192.168.16.70'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.16.71'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.16.71 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.16.71 prog 100005 vers 3 prot UDP port 1020
mount.nfs: an incorrect mount option was specified
[root@darkstar tmp [j0]#>>>
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Sat Dec 25 06:33:44 2010
mount.nfs: trying text-based options 'vers=4,addr=192.168.16.71,clientaddr=192.168.16.70'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.16.71'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.16.71 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.16.71 prog 100005 vers 3 prot UDP port 1020
192.168.16.71:/var/www/ on /tmp/hd type nfs (rw)
/etc/rc.d/rc.rpc odpalone? Wydaje mi się, że to musi działąć zarówna na kliencie jak i serwerze.
Zastrzegam sobie prawo nieanalizowania postów pisanych niepoprawną polszczyzną.
Post generated automatically by A.I. system code name ‘mina86’ in response to the previous one.
[root@darkstar tmp [j0]#>>> mount -v 192.168.16.71:/var/www/ /mnt/hd/
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Sat Dec 25 07:54:27 2010
mount.nfs: trying text-based options 'vers=4,addr=192.168.16.71,clientaddr=192.168.16.70'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.16.71'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.16.71 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.16.71 prog 100005 vers 3 prot UDP port 1020
mount.nfs: an incorrect mount option was specified
[root@darkstar tmp [j0]#>>>
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Sat Dec 25 06:33:44 2010
mount.nfs: trying text-based options 'vers=4,addr=192.168.16.71,clientaddr=192.168.16.70'
mount.nfs: mount(2): Protocol not supported
mount.nfs: trying text-based options 'addr=192.168.16.71'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.16.71 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.16.71 prog 100005 vers 3 prot UDP port 1020
192.168.16.71:/var/www/ on /tmp/hd type nfs (rw)
Co moze byc przyczyna tego zachowania?
Pozdrawiam
Witam Wesołych Świąt!... w składni polecenia mount po co dajesz -v skoro nie definujesz typu? czy montowany zasób ma odpowiednie prawa? Wykanaj na kliencie
Zastrzegam sobie prawo nieanalizowania postów pisanych niepoprawną polszczyzną.
Post generated automatically by A.I. system code name ‘mina86’ in response to the previous one.