| Summary: | dev-db/postgresql-base-9.1.3 ebuild and /var/run vs /run | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jimmy.Jazz |
| Component: | New packages | Assignee: | PgSQL Bugs <pgsql-bugs> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
/var/run is moving/has moved to /run.
The PostgreSQL ebuilds are doing the right thing.
You can define unix_socket_directory in /etc/postgresql-${SLOT}/postgresql.conf to a location other than /run/postgresql.
(In reply to comment #1) > /var/run is moving/has moved to /run. > > The PostgreSQL ebuilds are doing the right thing. > > You can define unix_socket_directory in > /etc/postgresql-${SLOT}/postgresql.conf to a location other than > /run/postgresql. FYI /run isn't a standard/conventional directory. Also it is created when gnome is installed on your computer because of udisks. Even if unix_socket_directory is set in postgresql.conf to /var/run/postgresql, the ebuild will just test the presence of /run and create the directory at the wrong place. RUNDIR has to be a global variable, so the admin could force it... and help PostgreSQL ebuilds to do the right thing. Please reconsider your point of view |
Please could the ebuild call a more flexible method like a default shell variable : ${RUNDIR:=/var} to define if the admin wants /run or /var/run for postgresql ? The actual ebuild will pick the wrong decision if /run exists. udisks 2.0 has /run hard coded (seems a 21 century style of programming) and will use it for ... medias. My computer, its scripts, my feelings, whatever still need /var/run for the daemons. Thank you