Mount and Share Conflicts
You can define a mount or a share so that a specified directory is mounted or shared Now (current), At Boot, or both Now and At Boot. Depending on your environment, different properties for each of these mounts and share states may be defined.
- Solaris stores At Boot mount properties in the /etc/vfstab table, and Now (current) mount properties in a dynamic pseudo table called /etc/mnttab. This latter table is generated by the mount command, and should not be edited directly.
- At Boot share properties are stored in the /etc/dfs/dfstab table, and Now (current) share properties in a dynamic pseudo table called /etc/dfs/sharetab. This latter table is generated by the share command, and should not be edited directly.
It is possible, therefore, to encounter a situation in which the properties for mounting or sharing At Boot are different from those for mounting or sharing Now. When this happens, the Mounts/Shares tool indicates that a particular mount or share is in conflict.
In most cases, it is desirable to keep your mounts and shares in synch -- that is, to not have any conflicts -- so that Now and At Boot properties are the same. However, there are some situations in which having your mounts and/or shares out of synch is desirable; for example when you want to mount a directory on a temporary basis for an installation, or share a directory for a relatively rare set of file transactions.
In the Mounts/Shares tool, when you double-click a mount or share, a Properties dialog box opens. If the mount or share you double-clicked is in conflict, you are asked which set of properties you want to view.
To resolve a conflict, click the desired mount or share, and then click Action->Resolve Conflict. You are asked which set of properties you want to use; the properties you choose will then be used for both the Now and At Boot properties for that mount or share.