Your message dated Sun, 13 Aug 2017 17:46:49 +0200 with message-id <[email protected]> and subject line Re: Bug#694454: ... and PAM, too has caused the Debian Bug report #694454, regarding pg_ctlcluster should have support for numactl and PAM to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 694454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694454 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: postgresql-common Version: 134 Severity: wishlist We should probably consider adding something like the following patch to pg_ctlcluster. It wraps pg_ctl using numactl. Other uses might be strace, gdb, and similar things. /etc/postgresql/*/*/pg_ctl.conf seems like the right spot to configure this, for example using pg_ctl_wrapper = '...' === modified file 'pg_ctlcluster' --- pg_ctlcluster 2012-11-04 21:39:47 +0000 +++ pg_ctlcluster 2012-11-26 14:31:25 +0000 @@ -171,7 +171,7 @@ # only supply or default logfile path when none is given explicitly in # postgresql.conf - @options = ($pg_ctl, 'start', '-D', $info{'pgdata'}); + @options = ('/usr/bin/numactl', '--interleave=all', $pg_ctl, 'start', '-D', $info{'pgdata'}); $logsize = 0; if ($info{'logfile'}) { push @options, ('-l', $info{'logfile'}); @@ -195,7 +195,7 @@ # without this, you'll get zombies on startup dup2(POSIX::open('/dev/null', POSIX::O_WRONLY), 1); dup2(POSIX::open('/dev/null', POSIX::O_WRONLY), 2); - exec $pg_ctl @options or error "could not exec $pg_ctl @options: $!"; + exec '/usr/bin/numactl', @options or error "could not exec /usr/bin/numactl @options: $!"; } # wait a bit until the socket exists Christoph -- [email protected] | http://www.df7cb.de/
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---Re: To [email protected] 2012-12-28 <[email protected]> > Here's yet another idea which will touch the same code region: > pg_ctlcluster should support PAM, or more specifically pam_limits.so, > so people can set proper limits in /etc/security/limits.conf. > > This is probably the easiest to achieve if we simply use su(1) instead > of doing the PID change etc in pure perl. In times of systemd, the proper way to set limits and friends is to drop a unit file snipped into /etc/systemd. Hacking pg_ctlcluster to handle even more corner cases seems like a dead end, closing my bug now. Christoph
--- End Message ---
_______________________________________________ Pkg-postgresql-public mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-postgresql-public
