public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Daniel_Casey@jbhunt.com
Cc: cygwin@cygwin.com
Subject: RE: nfs server
Date: Wed, 14 May 2003 00:25:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.44.0305131954520.17480-100000@slinky.cs.nyu.edu> (raw)
In-Reply-To: <OF2AC9D0B7.78C6782A-ON86256D25.007AB3BC-86256D25.007B0550@jbhunt.com>

On Tue, 13 May 2003 Daniel_Casey@jbhunt.com wrote:

> This is how the nfs-server-config script does it:
>
> # Install portmap service
> echo "Installing portmap as '$PMAP_D'"
> cygrunsrv.exe -I "portmap" -d "$PMAP_D" -f "$PMAP_F" -p /usr/sbin/portmap -e CYGWIN=ntsec -a "-F"
>
> # Install mountd service
> echo "Installing mountd as '$MNTD_D'"
> cygrunsrv.exe -I "mountd" -d "$MNTD_D" -f "$MNTD_F" -p /usr/sbin/rpc.mountd -e CYGWIN=ntsec --dep portmap -a "-F"
>
> # Install nfsd service
> echo "Installing nfsd as '$NFSD_D'"
> cygrunsrv.exe -I "nfsd" -d "$NFSD_D" -f "$NFSD_F" -p /usr/sbin/rpc.nfsd -e CYGWIN=ntsec --dep portmap -a "-F"
>
> So, I should have those options already in there?

Yes.

> Something else I noticed is that the paths to the executable's in this
> script are
>
> /usr/sbin/rpc.nfsd, /usr/sbin/rpc.mountd and /usr/sbin/portmap
>
> But they are actually:
>
> /usr/sbin/rpc.nfsd.exe, /usr/sbin/rpc.mountd.exe and /usr/sbin/portmap.exe
>
> Does this matter?  I would think so, but just wanted to double check.

It doesn't.  So it looks like your problem is in the mounts...  Make them
system mounts, and it should work.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Knowledge is an unending adventure at the edge of uncertainty.
  -- Leto II


--
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/

  reply	other threads:[~2003-05-13 23:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 23:36 Daniel_Casey
2003-05-14  0:25 ` Igor Pechtchanski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-14 14:41 Daniel_Casey
2003-05-14 14:41 ` Igor Pechtchanski
2003-05-14  2:34 Robb, Sam
2003-05-14  3:40 ` Igor Pechtchanski
2003-05-13 22:25 Daniel_Casey
2003-05-14  0:01 ` Igor Pechtchanski
2003-05-13 21:39 Daniel_Casey
2003-05-13 21:53 ` Igor Pechtchanski
2003-05-13 21:25 Robb, Sam
2003-05-13 20:33 Robb, Sam
2003-05-13 20:31 Daniel_Casey
2003-05-13 20:23 Robb, Sam
2003-05-13 19:18 Daniel_Casey
2001-02-12 12:59 NFS server Fabio Fabbri
     [not found] <199708241719.MAA32270@cirrusnet.com>
1997-08-25  6:51 ` NFS Server Murat Demircioglu
1997-08-24 21:07 dahms
1997-08-25  6:51 ` Ron G. Minnich
1997-08-20 14:12 Murat Demircioglu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.44.0305131954520.17480-100000@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=Daniel_Casey@jbhunt.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).