On 06/22/13 19:48, Scott Marlowe wrote:
> On Sat, Jun 22, 2013 at 4:45 PM, Jan Wieck <janwieck at yahoo.com> wrote:
>> There is nothing laughable about your situation, so I don't know what you
>> LOL all the time.
> 
> It might be one of those laugh or cry things.
> 
>> Whoever installed that database and Slony system determined where the logs
>> go. Check the system startup scripts ans syslog files/configuration for any
>> hints. Unfortunately every Linux packager has his/her own mind where things
>> are supposed to go. Not like in half organized FreeBSD territory, where you
>> at least can guess where the logs may be.
> 
> To be fair, most distros put it all in a few common places. I.e.
> Redhat / rpm based or Debian / deb based.  And there's nothing
> stopping a BSD sysadmin from building postgresql ala ./configure
> --prefix=/home/mydir/are/you/kidding/me
> 

Fair enough. But then again, everyone can do that compiling from sources
(unless you try to imply that Linux sysadmins don't know any more how to
do that).

The points several people have made remain. Bambi has to follow the
system startup breadcrumbs to figure out where the log is, if he/she
intends to find out what is currently broken in order to fix the current
system

On the other hand, fixing that system "properly" means to upgrade
everything to the latest versions. Which should start with something
like "apt-get update" or "yum update" instead of attempting to just get
past the current "problem". I still have the feeling that Slony stopped
working because of a far greater underlying problem.


Jan

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin