I found that it depends on file permissions/ownership.
The construct:
open L, ">$default_log"; close L; # empty default log file
only works if you are the file owner.
The test is running as root and the open/close will fail to open the
postgres:adm opened file.
A simple test might look like:
use strict;
use warnings;
my $default_log = "/tmp/test";
system("rm $default_log");
system("echo 'SOME TEST CONTENT' > $default_log");
system("chmod 666 $default_log");
system("chown postgres:adm $default_log");
system("id");
system("/usr/bin/ls","-laF","$default_log");
system("echo","PRE");
system("/usr/bin/cat","$default_log");
open L, ">$default_log"; close L; # empty default log file
system("echo","POST");
system("/usr/bin/cat","$default_log");
I'm still missing the role of the new procps version in this, as the
above is the same in both procps versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864423
Title:
Failed test 'default log is not used' with new procps 3.3.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postgresql-common/+bug/1864423/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
