Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: nfs-server re-exporting mapped network drives Date: Fri, 12 Mar 2004 15:53:03 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <4051D96C.6080502@siemens.com> Message-ID: X-OriginalArrivalTime: 12 Mar 2004 15:53:04.0546 (UTC) FILETIME=[1AEB8020:01C4084A] > -----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/