[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: links to logs in /etc? (/etc/postgresql/7.4/main/log)


Wouter Verhelst [2005-06-15  1:29 +0200]:
> wouter@country:~$ ls -l /usr/bin/awk
> rwxr-xr-x  1 root root 21 2005-03-28 10:49 /usr/bin/awk -> /etc/alternatives/awk
> wouter@country:~$ ls -l /etc/alternatives/awk
> rwxr-xr-x  1 root root 13 2005-03-28 13:22 /etc/alternatives/awk -> /usr/bin/gawk
> In other words, alternatives are *never* directly read from
> /etc/alternatives; they are read from, e.g., /usr/bin/awk.
> If you have a symlink /var/log/app.log -> /etc/app/log, then you're
> fine. If your app is writing directly to /etc/app/log, you're not.
> Why? Because otherwise your application tries to open a file which it
> can lstat but not stat if whatever the symlink tries to write to is not
> available for some reason (e.g., the file system is b0rked or not
> mounted).

That doesn't happen, pg_ctlcluster supplies the real log file location
to the postmaster:

sub cluster_info {
    my %result;
    $result{'configdir'} = "$confroot/$_[0]/$_[1]";
    $result{'logfile'} = readlink ($result{'configdir'} . "/log");

As I said, I only regard the symlink target as configuration value, I
don't actually pretend that the actual log file is in /etc.


Martin Pitt        http://www.piware.de
Ubuntu Developer   http://www.ubuntu.com
Debian Developer   http://www.debian.org

Attachment: signature.asc
Description: Digital signature

Reply to: