11-10-2007
Quote:
Originally Posted by
blesets
Can you explain to me? why it could happen.
You would need to analyse your system boot up, I suggest start with the system message log.
10 More Discussions You Might Find Interesting
1. Solaris
I have a NFS share on a Linux server. When I try to mount it on a Solaris 9 server, I get the following message:
nfs mount: <nfs-server-name>: : RPC: Program not registered
I have a few other Sun boxes and I can mount the share on them without any problems. (2 Replies)
Discussion started by: soliberus
2 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I'm trying to create an NFS mount on server1 to server2. From the man pages I think I'm doing it right:
mount server2:/dev/vg60/lvol607 /net1
nfs mount: server1:/dev/vg60/lvol607: Permission denied
Do I need to provide login credentials to server 2 somehow? What am I missing?
... (1 Reply)
Discussion started by: FredSmith
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
Following my last post I've mounted the remote server on my local server. However copying files from this mounted server is increadbily slow. If I copy files using rcp it's very fast so I assume there must be a setting somewhere?
Any help appreicated.
Thanks (2 Replies)
Discussion started by: AngryBunny
2 Replies
4. UNIX for Advanced & Expert Users
This is an unusual situation where I have an NFS server currently serving out MULTIPLE clients over several variants of Linux and UNIX successfully (world permissions) except for a SINGLE client. Even the other Linux (SuSE) clients in the same room are mounting successfully with defaults without... (6 Replies)
Discussion started by: neelpert1
6 Replies
5. 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
6. Red Hat
Hi Forum
I am trying to mount /NFS as nfs mountpoint on two servers ( A & B ).
After mounting the nfs filesystem, both of them behave normally for around 10 mins and after that the NFS file handle become stale and the
mountpoints dont respond. While executing df -kh, the output hang out and the... (15 Replies)
Discussion started by: rajdasuwal
15 Replies
7. Solaris
Dear All,
Struck with a peculiar problem
a) /opt/a is auto mounted to /home/a for User:a
When the User logs in to the server his home directory is getting mounted from the autofs i.e /home/a (/opt/a), Instead is has to mount the User home dir from NIS which is /home/a (from NIS).
... (2 Replies)
Discussion started by: saiprashant
2 Replies
8. 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
9. AIX
Hi,
I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error:
# mount 128.127.11.121:/aix /to_be_del
mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper
failure - RPC: 1832-008 Timed out
mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies
10. 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
LEARN ABOUT HPUX
bootconf
bootconf(4) Kernel Interfaces Manual bootconf(4)
NAME
bootconf - boot device configuration table
DESCRIPTION
The file contains the address and disk layout type of the system's boot devices or lif volumes. It is used by the and HP-UX kernel control
scripts (fileset to determine how and where to update the initial boot loader. Normally the kernel's script queries the system's hardware
and creates the file. In rare cases when either the system configuration cannot be automatically determined or additional and/or alternate
boot devices should be automatically updated, the administrator must edit the file manually.
There is one line in the file for each boot device. Each line contains the following blank-separated fields in the order shown:
disk type A flag indicating how the file system(s) on the disk are laid out. The flag must be one of the following:
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format. If LVM or VxVM mirrors are used, then each of the "mirrors" must have its own line in the file.
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap space are reserved outside the file system.
device file The absolute path of the device special file that accesses the physical device where the boot area is located. For LVM root
disks, the device special file is the physical volume(s) returned by the command. For "whole disks" this is the device file
that references the entire disk.
Blank lines are permitted. Any line beginning with a is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file contains diagnostic messages under the fileset if the file is incorrect. Most of the messages are self-
explanatory; a few warrant additional explanation:
If there are no other messages about
the file is probably empty. Otherwise, the file is not in the proper format, and the other messages will explain what the problem
is.
The specified device file does not point to a disk where there is a
lif which contains the file
Some character other than
or is in the first field of a line.
As of release 10.0, the boot areas in
must all be on the same type of disk layout.
There are characters after the
device file specification.
EXAMPLES
The boot area is on an LVM root disk:
l /dev/disk/disk7_p2
The boot area is on a whole disk layout:
w /dev/disk/disk7
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
was developed by the Hewlett-Packard Company.
FILES
SEE ALSO
mediainit(1), hpux(1M), hpux.efi(1M), mkboot(1M), vgdisplay(1M), lif(4), intro(7).
documentation.
bootconf(4)