nfs-server re-exporting mapped network drives
The file nfs-server-2.2.47-2.README states: If you want your mount and NFS daemons to re-export mapped network drives, you will need to run them under an account other than Local System, and start both daemons with the '-r' option to enable re-exporting. I was able to install the daemons using the -r option with my usual login account (which also works for mapping network drives). However when I try to start them in the services gui I get an error stating the program terminated unexpectedly and the windows event log is no more helpful. I don't have a problem if I install/start the daemons without -r under the default LocalSystem rather than my own account. Is this a possible bug in the nfsd/mountd daemons or is it actually rejecting my account at start-time? (I get no complaints when I enter my uid/password+password.) If it it rejecting my account, what type of permissions do I need to be able to do this? cygcheck attached. Thanks, -gene Cygwin Win95/NT Configuration Diagnostics Current System Time: Fri Mar 12 10:07:21 2004 Windows 2000 Professional Ver 5.0 Build 2195 Service Pack 4 Path: C:\cygwin\usr\local\bin C:\cygwin\bin C:\cygwin\bin C:\cygwin\usr\X11R6\bin c:\WINNT\system32 c:\WINNT c:\WINNT\System32\Wbem Output from C:\cygwin\bin\id.exe (nontsec) UID: 17951(SMITED) GID: 10545(mkgroup-l-d) 10545(mkgroup-l-d) Output from C:\cygwin\bin\id.exe (ntsec) UID: 17951(SMITED) GID: 10545(mkgroup-l-d) 0(root) 544(Administrators) 545(Users) 10545(mkgroup-l-d) SysDir: C:\WINNT\system32 WinDir: C:\WINNT HOME = `c:\Documents and Settings\SMITED' MAKE_MODE = `unix' PWD = `/var/log' USER = `SMITED' ALLUSERSPROFILE = `C:\Documents and Settings\All Users' APPDATA = `C:\Documents and Settings\SMITED\Application Data' COLORFGBG = `0;default;15' COLORTERM = `rxvt-xpm' COMMONPROGRAMFILES = `C:\Program Files\Common Files' COMPUTERNAME = `04J005' COMSPEC = `C:\WINNT\system32\cmd.exe' CVS_RSH = `/bin/ssh' DISPLAY = `:0' HOMEDRIVE = `C:' HOMEPATH = `\Documents and Settings\SMITED' HOSTNAME = `04J005' INFOPATH = `/usr/local/info:/usr/info:/usr/share/info:/usr/autotool/devel/info:/usr/autotool/stable/info:' LOGONSERVER = `\\JSC0006D' MANPATH = `/usr/local/man:/usr/man:/usr/share/man:/usr/autotool/devel/man::/usr/ssl/man' NUMBER_OF_PROCESSORS = `1' OLDPWD = `/var' OS2LIBPATH = `C:\WINNT\system32\os2\dll;' OS = `Windows_NT' PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = `x86' PROCESSOR_IDENTIFIER = `x86 Family 15 Model 2 Stepping 9, GenuineIntel' PROCESSOR_LEVEL = `15' PROCESSOR_REVISION = `0209' PROGRAMFILES = `C:\Program Files' PROMPT = `$P$G' PS1 = `\[\033]0;\w\007 [EMAIL PROTECTED] \[\033[33m\w\033[0m\] $ ' SHELL = `/bin/bash' SHLVL = `1' SYSTEMDRIVE = `C:' SYSTEMROOT = `C:\WINNT' TEMP = `c:\DOCUME~1\SMITED\LOCALS~1\Temp' TERM = `xterm' TMP = `c:\DOCUME~1\SMITED\LOCALS~1\Temp' USERDOMAIN = `SEA' USERNAME = `SMITED' USERPROFILE = `C:\Documents and Settings\SMITED' WINDIR = `C:\WINNT' WINDOWID = `168047280' _ = `/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygnus Solutions HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2 HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\00 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\01 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\02 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\03 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\04 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\05 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\06 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\07 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\08 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\09 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0A HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0B HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0C HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0D HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0E HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\0F HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\10 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\11 HKEY_CURRENT_USER\Software\Cygnus Solutions\CYGWIN.DLL setup\b15.0\mounts\12
RE: nfs-server re-exporting mapped network drives
-Original Message- From: cygwin-owner On Behalf Of Smith, Gene Sent: 12 March 2004 15:38 The file nfs-server-2.2.47-2.README states: If you want your mount and NFS daemons to re-export mapped network drives, you will need to run them under an account other than Local System, and start both daemons with the '-r' option to enable re-exporting. I was able to install the daemons using the -r option with my usual login account (which also works for mapping network drives). However when I try to start them in the services gui I get an error stating the program terminated unexpectedly and the windows event log is no more helpful. I don't have a problem if I install/start the daemons without -r under the default LocalSystem rather than my own account. Is this a possible bug in the nfsd/mountd daemons or is it actually rejecting my account at start-time? (I get no complaints when I enter my uid/password+password.) If it it rejecting my account, what type of permissions do I need to be able to do this? cygcheck attached. Thanks, -gene It's most likely that the programs are actually starting OK but erroring out almost at once. You haven't tried the obvious experiments yet: what happens when you install them *with* -r under LocalSystem? What happens when you install them *without* -r under your usual login account? You've changed two things at one time: the command line flags, and the account under which it runs. You'll have to revert one of them to find out which of them caused the problem. Having said that, it's likely to be a Win ACL/privs problem. If you edit your local security policy to enable auditing of failures for all events, you may well get some useful information in your event viewer (security log) next time you try and start the server. It will certainly show up if the daemons are trying something that requires privileges enabled that they don't have. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: nfs-server re-exporting mapped network drives
Dave Korn wrote: -Original Message- From: cygwin-owner On Behalf Of Smith, Gene Sent: 12 March 2004 15:38 The file nfs-server-2.2.47-2.README states: If you want your mount and NFS daemons to re-export mapped network drives, you will need to run them under an account other than Local System, and start both daemons with the '-r' option to enable re-exporting. I was able to install the daemons using the -r option with my usual login account (which also works for mapping network drives). However when I try to start them in the services gui I get an error stating the program terminated unexpectedly and the windows event log is no more helpful. I don't have a problem if I install/start the daemons without -r under the default LocalSystem rather than my own account. Is this a possible bug in the nfsd/mountd daemons or is it actually rejecting my account at start-time? (I get no complaints when I enter my uid/password+password.) If it it rejecting my account, what type of permissions do I need to be able to do this? cygcheck attached. Thanks, -gene It's most likely that the programs are actually starting OK but erroring out almost at once. You haven't tried the obvious experiments yet: what happens when you install them *with* -r under LocalSystem? What happens when you install them *without* -r under your usual login account? You've changed two things at one time: the command line flags, and the account under which it runs. You'll have to revert one of them to find out which of them caused the problem. Having said that, it's likely to be a Win ACL/privs problem. If you edit your local security policy to enable auditing of failures for all events, you may well get some useful information in your event viewer (security log) next time you try and start the server. It will certainly show up if the daemons are trying something that requires privileges enabled that they don't have. cheers, DaveK When I do -r with LocalSystem, all daemons start and I can mount as expected on remote computer, but can't see the mapped drive (which I have mounted on the computer running nfs-server into a new directory off / as described in the cyg/nfs readme. Running mount -m on the nfs-server computer all show -s (system/global) mounts. When I run without -r and use my usual NT account, I get the same result as running with -r and my usual NT account. Daemons fail to start. I enabled the security audit log but the only time I see a failure there is when I intentionally put in a bad password when prompted. Otherwise, no security errors when using my own account. I tried installing/starting portmap with my nt account and it would not go at all until I put it back to LocalSystem. (I have had no problems starting portmap until I tried this.) I do see a bit more detail in the application log for nfsd and mountd when they fail to start under my account. They both produce 2 log entries (4 total) when they fail (see attached). I have included the ones for nfsd. The ones for mountd are very similar so I did not include them. I notice that the app log refers to /var/log files. In /var/log the nfsd, portmap and mountd log files are owner/group = SYSTEM/root. Could this be significant? The only one containing data is nfsd.log but nothing in it seem to pertain to my problem, since the data only went in, apparently, when it was working right (with LocalSystem account). Any more ideas? -gene Event Type: Error Event Source: nfsd Event Category: None Event ID: 0 Date: 3/12/2004 Time: 2:07:26 PM User: SEA\SMITED Computer: 04J005 Description: The description for Event ID ( 0 ) in Source ( nfsd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: nfsd : PID 2320 : starting service `m' failed: redirect_fd: open (1, /var/log/nfsd.log): 13, Permission denied. Event Type: Error Event Source: nfsd Event Category: None Event ID: 0 Date: 3/12/2004 Time: 2:07:27 PM User: SEA\SMITED Computer: 04J005 Description: The description for Event ID ( 0 ) in Source ( nfsd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: nfsd : PID 2336 : starting service `nfsd' failed: execv: 1, Operation not permitted. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: nfs-server re-exporting mapped network drives
On Fri, 12 Mar 2004, Smith, Gene wrote: Dave Korn wrote: -Original Message- From: cygwin-owner On Behalf Of Smith, Gene Sent: 12 March 2004 15:38 The file nfs-server-2.2.47-2.README states: If you want your mount and NFS daemons to re-export mapped network drives, you will need to run them under an account other than Local System, and start both daemons with the '-r' option to enable re-exporting. I was able to install the daemons using the -r option with my usual login account (which also works for mapping network drives). However when I try to start them in the services gui I get an error stating the program terminated unexpectedly and the windows event log is no more helpful. I don't have a problem if I install/start the daemons without -r under the default LocalSystem rather than my own account. Is this a possible bug in the nfsd/mountd daemons or is it actually rejecting my account at start-time? (I get no complaints when I enter my uid/password+password.) If it it rejecting my account, what type of permissions do I need to be able to do this? cygcheck attached. Thanks, -gene It's most likely that the programs are actually starting OK but erroring out almost at once. You haven't tried the obvious experiments yet: what happens when you install them *with* -r under LocalSystem? What happens when you install them *without* -r under your usual login account? You've changed two things at one time: the command line flags, and the account under which it runs. You'll have to revert one of them to find out which of them caused the problem. Having said that, it's likely to be a Win ACL/privs problem. If you edit your local security policy to enable auditing of failures for all events, you may well get some useful information in your event viewer (security log) next time you try and start the server. It will certainly show up if the daemons are trying something that requires privileges enabled that they don't have. cheers, DaveK When I do -r with LocalSystem, all daemons start and I can mount as expected on remote computer, but can't see the mapped drive (which I have mounted on the computer running nfs-server into a new directory off / as described in the cyg/nfs readme. Running mount -m on the nfs-server computer all show -s (system/global) mounts. When I run without -r and use my usual NT account, I get the same result as running with -r and my usual NT account. Daemons fail to start. I enabled the security audit log but the only time I see a failure there is when I intentionally put in a bad password when prompted. Otherwise, no security errors when using my own account. I tried installing/starting portmap with my nt account and it would not go at all until I put it back to LocalSystem. (I have had no problems starting portmap until I tried this.) I do see a bit more detail in the application log for nfsd and mountd when they fail to start under my account. They both produce 2 log entries (4 total) when they fail (see attached). I have included the ones for nfsd. The ones for mountd are very similar so I did not include them. I notice that the app log refers to /var/log files. In /var/log the nfsd, portmap and mountd log files are owner/group = SYSTEM/root. Could this be significant? The only one containing data is nfsd.log but nothing in it seem to pertain to my problem, since the data only went in, apparently, when it was working right (with LocalSystem account). Any more ideas? -gene Event Type: Error Event Source: nfsd Event Category: None Event ID: 0 Date: 3/12/2004 Time: 2:07:26 PM User: SEA\SMITED Computer: 04J005 Description: The description for Event ID ( 0 ) in Source ( nfsd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: nfsd : PID 2320 : starting service `m' failed: redirect_fd: open (1, /var/log/nfsd.log): 13, Permission denied. Hmm, this one should be pretty obvious -- a chmod a+w /var/log/nfsd.log should fix this right up. Igor Event Type: Error Event Source: nfsd Event Category: None Event ID: 0 Date: 3/12/2004 Time: 2:07:27 PM User: SEA\SMITED Computer: 04J005 Description: The description for Event ID ( 0 ) in Source ( nfsd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: nfsd : PID 2336 : starting service `nfsd' failed: execv: 1, Operation not permitted. -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ [EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-'Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a
Re: nfs-server re-exporting mapped network drives
Igor Pechtchanski wrote: Event Type: Error Event Source: nfsd Event Category: None Event ID: 0 Date: 3/12/2004 Time: 2:07:26 PM User: SEA\SMITED Computer: 04J005 Description: The description for Event ID ( 0 ) in Source ( nfsd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: nfsd : PID 2320 : starting service `m' failed: redirect_fd: open (1, /var/log/nfsd.log): 13, Permission denied. Hmm, this one should be pretty obvious -- a chmod a+w /var/log/nfsd.log should fix this right up. Igor You are right! That fixed it. There was already a w for the user SYSTEM but not on group and other. Guess that's what it needs. This fact should definitely be added to the readme or changed in the default install. I changed it on all three nfs related log files for good measure. I also noticed that nfs-server-config script did not work quite right the second time you ran it. It would not reload the daemons but complain they were already installed. I fixed that my rearranging the order of things. Also, it always complained that your mounts were not global even when they are. I also fixed that. Should I send a patch to someone or just send my fixed file to this list? Thanks for the help. -gene -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: nfs-server re-exporting mapped network drives
On Fri, 12 Mar 2004, Smith, Gene wrote: Igor Pechtchanski wrote: Event Type: Error Event Source: nfsd Event Category: None Event ID: 0 Date: 3/12/2004 Time: 2:07:26 PM User: SEA\SMITED Computer: 04J005 Description: The description for Event ID ( 0 ) in Source ( nfsd ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: nfsd : PID 2320 : starting service `m' failed: redirect_fd: open (1, /var/log/nfsd.log): 13, Permission denied. Hmm, this one should be pretty obvious -- a chmod a+w /var/log/nfsd.log should fix this right up. Igor You are right! That fixed it. There was already a w for the user SYSTEM but not on group and other. Guess that's what it needs. This fact should definitely be added to the readme or changed in the default install. I changed it on all three nfs related log files for good measure. The log files are created by cygrunsrv when the service is first started. If cygrunsrv ran as LocalSystem, the logs will be owned by LocalSystem. The default umask (set in /etc/profile) is 022, which means turn off group and world write permissions. I doubt there's anything the nfs server itself can do about this. You might try changing the umask in /etc/profile, removing the log, and starting over... If this works, then it definitely should be in the README. I also noticed that nfs-server-config script did not work quite right the second time you ran it. It would not reload the daemons but complain they were already installed. I fixed that my rearranging the order of things. Also, it always complained that your mounts were not global even when they are. I also fixed that. Should I send a patch to someone or just send my fixed file to this list? Thanks for the help. -gene The nfs-server announcement (http://cygwin.com/ml/cygwin/2003-11/msg00267.html) says to send comments and questions to the cygwin list (i.e., here). To help the maintainer filter out the relevant messages, you might put something like [PATCH] nfs-server: ... as the subject. Hope this helps, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: nfs-server re-exporting mapped network drives
Igor Pechtchanski wrote: On Fri, 12 Mar 2004, Smith, Gene wrote: You are right! That fixed it. There was already a w for the user SYSTEM but not on group and other. Guess that's what it needs. This fact should definitely be added to the readme or changed in the default install. I changed it on all three nfs related log files for good measure. The log files are created by cygrunsrv when the service is first started. If cygrunsrv ran as LocalSystem, the logs will be owned by LocalSystem. The default umask (set in /etc/profile) is 022, which means turn off group and world write permissions. I doubt there's anything the nfs server itself can do about this. You might try changing the umask in /etc/profile, removing the log, and starting over... If this works, then it definitely should be in the README. Changed umask in /etc/profile to 000. With nfs daemons running, rm'd the logfiles. Restarted daemons with no error. Files came back like this: -rw-r--r--1 SMITED mkgroup-0 Mar 12 17:18 mountd.log -rw-r--r--1 SMITED mkgroup-11869 Mar 12 17:21 nfsd.log -rw-r--r--1 SYSTEM root0 Mar 12 17:18 portmap.log No longer all SYSTEM/root but now like all other files in system SMITED/mkgroup- (except portmap which is still running as LocalSystem). Looks like the 1st time you start nfs as LocalSystem it makes it impossible to change unless you add write permissions or delete the mountd and ntfsd log files first. Also noticed that when I bop around in my mounted nfs directory on the client machine (doing cd's and ls), I get tons of errors in the nfsd.log file all saying this: nfsd[1860] 03/12/104 17:21 auth_clnt.c 327 : Unable to setgroups: invalid argument This happened when running as LocalSystem too. -gene I also noticed that nfs-server-config script did not work quite right the second time you ran it. It would not reload the daemons but complain they were already installed. I fixed that my rearranging the order of things. Also, it always complained that your mounts were not global even when they are. I also fixed that. Should I send a patch to someone or just send my fixed file to this list? Thanks for the help. -gene The nfs-server announcement (http://cygwin.com/ml/cygwin/2003-11/msg00267.html) says to send comments and questions to the cygwin list (i.e., here). To help the maintainer filter out the relevant messages, you might put something like [PATCH] nfs-server: ... as the subject. Hope this helps, Igor -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: nfs-server re-exporting mapped network drives
One other related question. When I setup my nfs-server that re-exports shares and enter my network password to get it going, will I need to restart the nfs daemons every few months when I am required to change my password? Or will the nfs daemons (services) keep going without requiring me to give them my new password? Even after a reboot? If I have to re-enter the password (actually you have to enter it 4 times, twice for mountd and twice for nfsd) it might be easier and less hassle just to mirror the shares on my local nfs-server machine and just export the mirrored directory and rsync the mirror dir to the network share periodically using cron. I would probably have better performance too. -gene -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
