Date: Sat, 19 Nov 2016 10:33:26 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 214663] databases/postgres95-server: FIB support not included in rc.d script Message-ID: <bug-214663-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214663 Bug ID: 214663 Summary: databases/postgres95-server: FIB support not included in rc.d script Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: rtd24@columbia.edu Created attachment 177179 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D177179&action= =3Dedit suggested patch for rc.d script When restarting postgresql server via rc scripts, the server's process inhe= rits the fib of the caller, ignoring any settings in /etc/rc.conf. During maintenance, this can cause headaches when simply restarting the database brings it up with the incorrect routing table. This is likely due to the rc script's use of 'su -l ${postgresql_user} -c "= exec ${command} ..." in the script. A simple fix is to insert "setfib ${postgresql_fib}" in the exec statment ; when no fib is configured, this will default to 0 in any case without any error. This is provided by the patch below. Caveat: this would break port installations on any OS prior to a base where /usr/sbin/setfib is not in use (but this was tested and found present on am= d64 versions as early as 7.2 =E2=80=93 may still want to modify to account for = early OS edge cases rather than calling setfib always implicitly) --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214663-13>