Mountd Daemon.error No Default Domain Set
Contents |
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword nfs server and client daemons in solaris 10 Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, nfs daemons in solaris 10 It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to how to restart nfs service in solaris 10 receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your
Solaris Nfs Mount Options
Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Sun: Solaris Forum at Tek-Tips HomeForumsMIS/ITOperating Systems - UNIX basedSun: Solaris Forum mountd[12314]: [ID 664212 daemon.error] No default domain set thread60-490253 Forum Search FAQs Links MVPs mountd[12314]: [ID 664212 daemon.error] No default domain set mountd[12314]: [ID 664212 daemon.error] No solaris nfs share default domain set spaigejr (MIS) (OP) 3 Mar 03 14:36 Can someone tell me why I see this message in /var/adm/messages.mountd[12314]: [ID 664212 daemon.error] No default domain set/etc/defaultdomain is not set, but we are not using NIS.I thought that was the only time the file was needed.Solaris 8 - kernel 18SunFire 6800ThanksSteve RE: mountd[12314]: [ID 664212 daemon.error] No default domain set bpinos (Programmer) 5 Mar 03 08:21 Are you sure that autofs is not running?Autofs trys to mount nfs shares when you try to access those directories.Make sure there aren't any auto_[something] in /etc.Those should be a moot point though if autofs is not running.You should eb able to safely shutdown autofs by running:/etc/init.d/autofs stopHope this helps! RE: mountd[12314]: [ID 664212 daemon.error] No default domain set Annihilannic (MIS) 5 Mar 03 08:59 It could be referring to a missing fully qualified domain name in /etc/resolv.conf perhaps? Annihilannic. RE: mountd[12314]: [ID 664212 daemon.error] No default domain set wtrepani (MIS) 7 Mar 03 11:31 It sounds almost like it is trying to pull the automount info from nis and the /etc/defaultdomain file is not present.check the /etc/nsswitch.c
Default Domain > Configuring an NFS Version 4 Default Domain in the Solaris 10 ReleaseSystem Administration Guide: Network ServicesPrevious: Configuring an NFS Version 4 Default Domain in the Solaris Express 5/06 ReleaseNext: Additional Information About nfsmapidConfiguring an NFS Version 4 Default Domain in the Solaris 10 ReleaseIn the initial Solaris 10 release of NFS version 4, if your network includes multiple DNS domains, but only has a single UID and GID namespace, all clients must use one value for NFSMAPID_DOMAIN. For sites that use DNS, nfsmapid resolves this http://www.tek-tips.com/viewthread.cfm?qid=490253 issue by obtaining the domain name from the value that you assigned to _nfsv4idmapdomain. For more information, see nfsmapid and DNS TXT Records. If your network is not configured to use DNS, during the first system boot the Solaris OS uses the sysidconfig(1M) utility to provide the following prompts for an NFS version 4 domain name: This system is configured with NFS https://docs.oracle.com/cd/E19082-01/819-1634/gbvgu/index.html version 4, which uses a domain name that is automatically derived from the system's name services. The derived domain name is sufficient for most configurations. In a few cases, mounts that cross different domains might cause files to be owned by nobody due to the lack of a common domain name. Do you need to override the system's default NFS verion 4 domain name (yes/no)? [no] The default response is [no]. If you choose [no], you see the following: For more information about how the NFS version 4 default domain name is derived and its impact, refer to the man pages for nfsmapid(1M) and nfs(4), and the System Administration Guide: Network Services. If you choose [yes], you see this prompt: Enter the domain to be used as the NFS version 4 domain name. NFS version 4 domain name []: Note – If a value for NFSMAPID_DOMAIN exists in /etc/default/nfs, the [domain_name] that you provide overrides that value. Previous: Configuring an NFS Version 4 Default Domain in the Solaris Express 5/06 ReleaseNext: Additional Information About nfsmapid © 2010, Oracle Corporation and/or its affiliates
FilesNext: NFS CommandsNFS Daemons To support NFS activities, several daemons are started when a system goes into run level 3 or multiuser mode. The mountd and nfsd daemons are run http://docs.oracle.com/cd/E19253-01/816-4555/6maoquics/index.html on systems that are servers. The automatic startup of the server daemons depends on the existence of entries that are labeled with the NFS file-system type in /etc/dfs/sharetab. To support NFS file locking, the lockd and statd daemons are run on NFS clients and servers. However, unlike previous versions of NFS, in NFS version 4, the daemons lockd, statd, mountd, in solaris and nfslogd are not used. This section describes the following daemons. automountd Daemon lockd Daemon mountd Daemon nfs4cbd Daemon nfsd Daemon nfslogd Daemon nfsmapid Daemon statd Daemon automountd Daemon This daemon handles the mounting and unmounting requests from the autofs service. The syntax of the command is as follows: automountd [ -Tnv ] [ -D name=value ] The command behaves in solaris 10 in the following ways: -T enables tracing. -n disables browsing on all autofs nodes. -v selects to log all status messages to the console. -D name=value substitutes value for the automount map variable that is indicated by name. The default value for the automount map is /etc/auto_master. Use the -T option for troubleshooting. lockd Daemon This daemon supports record-locking operations on NFS files. The lockd daemon manages RPC connections between the client and the server for the Network Lock Manager (NLM) protocol. The daemon is normally started without any options. You can use three options with this command. See the lockd(1M) man page. These options can either be used from the command line or by editing the appropriate string in /etc/default/nfs. The following are descriptions of keywords that can be set in the /etc/default/nfs file. Note – Starting in the Solaris 10 release, the LOCKD_GRACE_PERIOD keyword and the -g option have been deprecated. The deprecated keyword is replaced with the new keyword GRACE_PERIOD. If both keywords are set, the value for GRACE_PERIOD overrides the value for LOCKD_GRACE_PERIOD.