X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: MIME-Version: 1.0 In-Reply-To: <5580f60e0912090801i1508abb7i52d09ebc1909bd9@mail.gmail.com> References: <1ef5a52f0912090205v2b8bb67cgcca943b8e64061f1 AT mail DOT gmail DOT com> <5580f60e0912090801i1508abb7i52d09ebc1909bd9 AT mail DOT gmail DOT com> Date: Wed, 9 Dec 2009 11:42:36 -0500 Subject: Re: 1.5.25-15: Problem running rpmbuild from a bash script From: Matt Rice To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Wed, Dec 9, 2009 at 11:01 AM, Matt Rice wrote: > That may very well be. =A0But I can't really determine anything because > I get no error messages. > > Also, I got desperate, so I uninstalled cygwin, changed some > permissions on the root cygwin directory, then reinstalled. =A0Now I'm > able to run the bash command in a windows prompt. =A0However, I'm > ashamed to say this wasn't my real problem. =A0Currently, I have a > Bamboo windows service running (under the SYSTEM account). =A0This > process is what calls bash.exe. =A0I thought since the windows prompt > was acting the same way, fixing one would fix both. =A0I was obviously > wrong. > > I know that there are issues with sshd running on 2003 under SYSTEM. > Could this be the same issue? =A0Is there anything I can do to get more > information from the failed command? Well, I tried adding SYSTEM to the create token object policy, and restarted the Bamboo service for the heck of it. Now it appears everything is working fine. I removed SYSTEM from the policy and restarted the service again just to make sure this was what was causing the issue. Apparently it wasn't, as it still works. So I'm not sure what fixed it, but sorry for spamming the list. Thanks, Matt -- 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