X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type :content-transfer-encoding; q=dns; s=default; b=o76i+G8QC2kLFO3y xT3y7WemwClD4yrbpNbMyORemMym7zpzlFsH3q3wwSXromyD4tR1e4j1QwPEVZDZ OS4LCefO7bS0mZQDvx4m/f4GTngxLdCmBE/K1+b9+vNuiU7iJrkogohdDlxLA/QT 6aWngErL8UrJvl/+pAFLNVyFrkQ= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type :content-transfer-encoding; s=default; bh=9xcKQDrDFIe09jKCO1TEMR j9tuI=; b=fmrfPrk632Bzd40J8h19gK8u1MAjtBrnXYScNvJXrydwlSV9KFuNsX o7dl4ZCAD15nofASDHDNgc8agpAZu3snkazYDQNwsZIfEk/MDKYgkZpz68tlwT80 9XwGeTm+H4juNuxtsiv71a0gc5fhGmSUVEJl9b1sv6CL3+0RulQIs= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 X-Spam-SWARE-Status: No, score=-3.5 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS,TW_NL autolearn=ham version=3.3.1 MIME-Version: 1.0 X-Received: by 10.50.102.41 with SMTP id fl9mr8231002igb.18.1369794226787; Tue, 28 May 2013 19:23:46 -0700 (PDT) In-Reply-To: <20130528185553.GA31309@calimero.vinschen.de> References: <20130528185553 DOT GA31309 AT calimero DOT vinschen DOT de> Date: Tue, 28 May 2013 22:23:46 -0400 Message-ID: Subject: Re: Using native symlinks From: Chris Sutcliffe To: The Cygwin Mailing List Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id r4T2O2cS030072 On 28 May 2013 14:55, Corinna Vinschen wrote: > On May 28 14:16, Chris Sutcliffe wrote: >> What permissions do I need for native symlinks to work? According to >> edit rights I have SeCreateSymbolicLinkPrivilege (when checking via an >> elevated shell - i.e. with "Run as Administrator"): >> >> ┌─┤ csutclif AT bmotec3017201lt ├──┤ ~ │ >> └─┤ 14:11 ├─>> editrights -u $USER -l >> SeLockMemoryPrivilege >> SeCreateSymbolicLinkPrivilege >> >> However, if I try and create a native symlink it still fails. If >> using the winsymlink:native option I get a "cygwin" symlink, winln > > That's "winsymlinks:native" I hope... Correct, I mistyped. >> pops up a message stating I need the SeCreateSymbolicLinkPrivilege. >> Not sure if it's relevant or not, but the $USER in this case is a >> domain user, not a local user. > > Are you sure it's an elevated shell? `id -G' should contain 544. Is > the filesystem NTFS? Is it a local NTFS or a remote NTFS hosted by a > Vista-or-later OS? If you set CYGWIN=winsymlink It works fine if I create the native symlinks in an elevated shell, but does not if I create the native symlinks in a "normal" shell. Is this expected (i.e. does creating native symlinks only work in elevated shells?). In this case the Domain user is a member of the local administrators group on the local machine. This filesystem is a local NTFS hosted on Windows 7. Thanks, Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d -- 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