Sponsored Content
Operating Systems Solaris nfs export not working at boot Post 302471761 by jalite19 on Monday 15th of November 2010 04:09:02 AM
Old 11-15-2010
manually export after booted via 'exportall' works fine, problem was only at boot time.
Is there any log might tell something? I checked dmsg and messages file but couldn't find anything from there?
 

10 More Discussions You Might Find Interesting

1. HP-UX

nfs export permissions

Hello, If I have an export like: /usr/temp -rw=ram:alligator means that /usr/temp has "rw" permissions to ram and alligator machines and has "ro" to everyone else? (1 Reply)
Discussion started by: psimoes79
1 Replies

2. Filesystems, Disks and Memory

Is it possible to re-export a exported NFS file system?

Hi... Is it possible to re-export a exported NFS file system? If no, Why? Let me know, if any further details are required about the question. Thanks in advance Adams:) (5 Replies)
Discussion started by: Adams Nave
5 Replies

3. Filesystems, Disks and Memory

NFS export filesystem with several partitions

I want to export the file system which consist of several partition. For example I export / and there are /home, /usr partitions. On client side I can see all files in /, but /home and /usr are empty. So far I failed to find the way to make other partitions visible in one mount. :confused: Of... (2 Replies)
Discussion started by: fmtu2005
2 Replies

4. Filesystems, Disks and Memory

Local NFS import / re-export using automount?

Hi, Can I do the following: On SunOS 5.8 /etc/vfstab: remote-host:/Volumes/webdata - /export/home/webdata nfs - yes rw,vers=3,soft,intr,bg,timeo=600 In /etc/auto_direct: /home/science $HOST:/export/home/webdata/science /home/science-edu ... (2 Replies)
Discussion started by: bloyall
2 Replies

5. Solaris

Could I re-export a NFS resource to a third server ?

Hey Guys. Could someone said if is possible take a NFS resource get it from a original Server a export it and mount it in a third server ? Thank in Advace.... SUN ADMIN (3 Replies)
Discussion started by: aggadtech08
3 Replies

6. UNIX for Advanced & Expert Users

NFS export need to be able to write to directory but not list

My issue is I want an NFS share where I can write to the directory, but not list any of the files in there. (doesn't matter if someone knows the name can open the file). Have an NFS export for example: drwxrwxrw- 2 cranes staff 256 18 May 12:48 cranes The export will only... (1 Reply)
Discussion started by: Cranie
1 Replies

7. AIX

nfs export

Hi How to export a file system from my aix box named ABC in such a way that everyone on the network should be able to import it When on the client side if they give showmount -e ABC it should show like this: # showmount -e ABC export list for ABC: /sybase/software (everyone) (2 Replies)
Discussion started by: newtoaixos
2 Replies

8. Red Hat

Understanding local access to NFS export

Hello, I've inherited an NFS setup that allows external servers to write to an NFS share on a Centos box. Here is an example line from /etc/exports (there are four entries that only are different based on server IP adress). /exports/foobar... (4 Replies)
Discussion started by: KickstartUF
4 Replies

9. Red Hat

CIFS share re-export NFS

Hi Guys, need help here. i have windows server that share a folder C:/ABCDE i configure samba client in Linux server as /EDCBA and it working fine. then i want to share this /EDCBA to another Linux server using NFS. in the /etc/exportfs i have put /EDCBA - *(rw,no_root_squash) ... (1 Reply)
Discussion started by: prossits
1 Replies

10. AIX

CIFS share re-export NFS

Hi Guys, need help here. i have windows server that share a folder C:/ABCDE i configure samba client in AIX server as /EDCBA and it working fine. then i want to share this /EDCBA to another AIX server using NFS. in the /etc/exportfs i have put /EDCBA... (1 Reply)
Discussion started by: prossits
1 Replies
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)
All times are GMT -4. The time now is 04:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy