Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Thu, 4 Sep 2003 09:15:03 -0400 From: Jason Tishler To: cygwin AT cygwin DOT com Subject: Re: suggestion for postgresql doc Message-ID: <20030904131503.GI1804@tishler.net> Mail-Followup-To: cygwin AT cygwin DOT com References: <16207 DOT 48166 DOT 70937 DOT 16643 AT tipi DOT mininet> <20030902120330 DOT GZ1680 AT tishler DOT net> <16212 DOT 65250 DOT 918369 DOT 614990 AT tipi DOT mininet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16212.65250.918369.614990@tipi.mininet> User-Agent: Mutt/1.4i Markus, On Tue, Sep 02, 2003 at 10:34:42PM +0200, Markus Hoenicka wrote: > Jason Tishler writes: > > What did you set the /var/log permissions to? Do the /tmp and > > /usr/bin comments above refer to Issue #2 and #4 in the following? > > > > http://www.tishler.net/jason/software/postgresql/postgresql-7.3.4.README > > > > I think I've used chmod a+rw (there might be a more secure way to deal > with this issue, though). I'm on vacation and my Cygwin setup is at > work so I have to apologize that I can't check right now. The original > permissions were from a fresh Cygwin installation that I did in the > last week of August. When using the original permissions, postmaster > refused to start with no trace of a log file which appears a bit > obscure to the unsuspecting user. Agreed. However, there should be an entry in the Event Log. Nevertheless, I will update my README. > Hope this helps It does. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or key servers Fingerprint: 7A73 1405 7F2B E669 C19D 8784 1AFD E4CC ECF4 8EF6 -- 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/