08-03-2009
Hi, I did not get you.
Currently i am able to mount the windows NFS share "share1" on one of the solaris box. I can see it in the df -k command as
10.10.10.11:/share1 13150912 56 13150856 1% /test1
while i do
#cd /test1
bash: cd: /test1" permission denied
the permission on test1 directory is
drwxrwxrwx 2 nobody nobody
Tx
---------- Post updated at 03:40 PM ---------- Previous update was at 02:17 PM ----------
This issue is resolved by giving the privilages to the system user "anonymous user" to the share.
Tx.
10 More Discussions You Might Find Interesting
1. AIX
Hello Everyone,
I have a pseries machine running AIX 4.3.3 that has an invalid IP in /etc/hosts. During a boot the system hangs because it's trying to mount an NFS share to this invalid IP.
I've tried to boot the system from a mksysb (not sure if the device was defined as rmt0) and AIX CD... (0 Replies)
Discussion started by: jlslhills
0 Replies
2. Solaris
Hi All
I am new for Solaris and, I have configured SAMBA on my SUN10 Network machine and it's working fine.
can anyone tell me how to mount windows share on my SUN10 machine.
Thanks in advance
daya (2 Replies)
Discussion started by: daya.pandit
2 Replies
3. UNIX for Advanced & Expert Users
this is probably a bit dumb ...but i read somewhere that one of the nfs versions can be mounted on a windows 2003 server ..if yes ..does anyone know how this can be achieved (1 Reply)
Discussion started by: tarunicon
1 Replies
4. IP Networking
Hello,
I have a few Ubuntu 9.10 laptops I'm trying to learn NFS sharing with. I am just experimenting on this right now, so no harsh words about the security of what I'm playing with, please ;)
Below are the configs
/etc/exports on host
/home/woodnt/Homeschool... (2 Replies)
Discussion started by: Narnie
2 Replies
5. Web Development
Hi,
I want to mount an NFS Shared folder on Windows XP to vxWorks.
There doesnt seem to be a problem with the sharing.
Now, when i try to mount the directory onto vxWorks (it runs on a Tumbleweed card), using a mount script (.sh), the following is the print i see on Tera Term:
hostAdd... (0 Replies)
Discussion started by: chinmayzen
0 Replies
6. Red Hat
When i tried to mount the nfs i see this error message
mount -t nfs 192.168.20.194:/remote/proj1 /nfsmount
mount: 192.168.20.194:/remote/proj1 failed, reason given by server: Permission denied
and the /etc/exports file in the host side looks like this
/remote/proj1 ... (12 Replies)
Discussion started by: srinathk
12 Replies
7. SCO
Hi! All,
I am trying to mount a NFS share on my FreeNAS system onto my SCO OpenServer 5.0.6. I get the following error:
mount: cannot mount /: Connection Refused (error 115)
Has anyone been able to do this? (3 Replies)
Discussion started by: trolley
3 Replies
8. Shell Programming and Scripting
I need a help of good people with effective bash script to mount nfs shared,
By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people.
The scenario as follow:
An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies
9. Solaris
I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
Discussion started by: Hiroshi
1 Replies
10. AIX
Right, now that I've finally worked out this website, I'll ask my question!
I am having an absolute nightmare with NFS on AIX. I have used it many times, and I know what I'm doing, however I cannot fathom what is going on here. I have 2 LPARs, sitting on the same physical host. They are... (12 Replies)
Discussion started by: tmooredba
12 Replies
WDMD(8) System Manager's Manual WDMD(8)
NAME
wdmd - watchdog multiplexing daemon
SYNOPSIS
wdmd [OPTIONS]
DESCRIPTION
This daemon opens /dev/watchdog and allows multiple independent sources to detmermine whether each KEEPALIVE is done. Every test interval
(10 seconds), the daemon tests each source. If any test fails, the KEEPALIVE is not done. In a standard configuration, the watchdog timer
will reset the system if no KEEPALIVE is done for 60 seconds ("fire timeout"). This means that if a single test fails 5-6 times in row,
the watchdog will fire and reset the system. With multiple test sources, fewer separate failures back to back can also cause a reset, e.g.
T seconds, P pass, F fail
T00: test1 P, test2 P, test3 P: KEEPALIVE done
T10: test1 F, test2 F, test3 P: KEEPALIVE skipped
T20: test1 F, test2 P, test3 P: KEEPALIVE skipped
T30: test1 P, test2 F, test3 P: KEEPALIVE skipped
T40: test1 P, test2 P, test3 F: KEEPALIVE skipped
T50: test1 F, test2 F, test3 P: KEEPALIVE skipped
T60: test1 P, test2 F, test3 P: KEEPALIVE skipped
T60: watchdog fires, system resets
(Depending on timings, the system may be reset sometime shortly before T60, and the tests at T60 would not be run.)
A crucial aspect to the design and function of wdmd is that if any single source does not pass tests for the fire timeout, the watchdog is
guaranteed to fire, regardless of whether other sources on the system have passed or failed. A spurious reset due to the combined effects
of multiple failing tests as shown above, is an accepted side effect.
The wdmd init script will load the softdog module if no other watchdog module has been loaded.
wdmd cannot be used on the system with any other program that needs to open /dev/watchdog, e.g. watchdog(8).
Test Source: clients
Using libwdmd, programs connect to wdmd via a unix socket, and send regular messages to wdmd to update an expiry time for their connection.
Every test interval, wdmd will check if the expiry time for a connection has been reached. If so, the test for that client fails.
Test Source: scripts
wdmd will run scripts from a designated directory every test interval. If a script exits with 0, the test is considered a success, other-
wise a failure. If a script does not exit by the end of the test interval, it is considered a failure.
OPTIONS
--version, -V
Print version.
--help, -h
Print usage.
--dump, -d
Print debug information from the daemon.
--probe, -p
Print path of functional watchdog device. Exit code 0 indicates a
functional device was found. Exit code 1 indicates a functional device
was not found.
-D
Enable debugging to stderr and don't fork.
-H 0|1
Enable (1) or disable (0) high priority features such as realtime
scheduling priority and mlockall.
-G name
Group ownership for the socket.
-S 0|1
Enable (1) or disable (0) script tests.
-s path
Path to scripts dir.
-k num
Kill unfinished scripts after num seconds.
-w path
The path to the watchdog device to try first.
2011-08-01 WDMD(8)