From a638588d7c24baffc81377ff8fdf4be0b77be15c Mon Sep 17 00:00:00 2001 From: Corinna Vinschen Date: Fri, 24 Sep 2004 09:47:10 +0000 Subject: [PATCH] * cygwinenv.sgml: smbntsec is not on by default. --- winsup/doc/ChangeLog | 4 ++++ winsup/doc/cygwinenv.sgml | 15 +++++++-------- 2 files changed, 11 insertions(+), 8 deletions(-) diff --git a/winsup/doc/ChangeLog b/winsup/doc/ChangeLog index 14b6b8caf..fff29ad0f 100644 --- a/winsup/doc/ChangeLog +++ b/winsup/doc/ChangeLog @@ -1,3 +1,7 @@ +2004-09-24 Corinna Vinschen + + * cygwinenv.sgml: smbntsec is not on by default. + 2004-09-14 Christopher Faylor * what.texinfo: Fix two typos reported on cygwin list. diff --git a/winsup/doc/cygwinenv.sgml b/winsup/doc/cygwinenv.sgml index f992e10b2..9ae2944fc 100644 --- a/winsup/doc/cygwinenv.sgml +++ b/winsup/doc/cygwinenv.sgml @@ -123,14 +123,13 @@ the documentation in . (no)smbntsec - if set, use ntsec on remote -drives as well (this is the default). If you encounter problems with NT shares -or Samba drives, setting this to nosmbntsec could help. In that -case the permission and owner/group information is faked as on FAT partitions. -A reason for a non working ntsec on remote drives could be -insufficient permissions of the users. Since the needed user rights are -somewhat dangerous (SeRestorePrivilege) it's not always an option to grant that -rights to users. However, this shouldn't be a problem in NT domain -environments. +drives as well (default is "nosmbntesc"). When setting "smbntsec" there's +a chance that you get problems with Samba shares so you should use this +option with care. One reason for a non working ntsec on +remote drives could be insufficient permissions of the users. The requires +user rights are somewhat dangerous (SeRestorePrivilege), so it's not always +an option to grant that rights to users. However, this shouldn't be a +problem in NT domain environments. (no)reset_com - if set, serial ports are reset