From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: [nfs-server] Hazardous changes introduced in 2.3-6
Date: Sun, 29 May 2016 13:59:00 -0000 [thread overview]
Message-ID: <9ad8f4ec-03c9-d959-4f64-e9ba9e29aec3@gmail.com> (raw)
In-Reply-To: <355417591.20160529023126@yandex.ru>
On 29/05/2016 01:31, Andrey Repin wrote:
> Greetings, jcwilson.cygwin@nym.hush.com!
>
>> I had installed the 3 cygrunsrv services (portmap, rpc.nfsd, rpc.mountd) to
>> use my login account as the services' user.
>
> That's your and only your mistake.
> I hope you've learned from it and will not repeat the same mistake again.
>
safety precaution should avoid that mistakes become tragedy...
In this case I agree with Josh that the default is hazardous if the user
don't select the default/proposed service userid.
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2016-05-29 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 2:40 jcwilson.cygwin
2016-05-29 8:54 ` Andrey Repin
2016-05-29 12:43 ` jcwilson.cygwin
2016-05-29 13:59 ` Marco Atzeri [this message]
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=9ad8f4ec-03c9-d959-4f64-e9ba9e29aec3@gmail.com \
--to=marco.atzeri@gmail.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).