Re: [gentoo-user] texlive 2011
On Tue, Dec 13, 2011 at 11:35:10AM -0800, Penguin Lover Alan E. Davis squawked: After realizing that most packages I was installing, I used package.keywords and ~amd64, so I went ahead and jumped---I have started using ACCEPT_KEYWORDS for ~amd64 in /etc/make.conf . I think most of the inconsistencies have been ironed out, but it has taken some days. One glaring problem involves ruby. I need texlive, and I want to install texlive 2011, and I had installed it; however, now ruby is standing in my way. Sorry, I am a bit confused about your description of what happened. Can you give us a concise timeline? (Like: Day 1 installed X. Day 3, changed keywords to ~amd64. Day 4, tried to install texlive. Got error message Blah.) On bugs.gentoo.org, I see some solutions, involving patches. One is a patch for ruby (dev-lang/ruby-1.8.7_p352 ). The other is a patch for glibc 2.14.1 . Which bug number? Now, unfortunately, after an emerge -avuD world, I have also run emerge --depclean, which cleared out every package involved with texlive. I think texlive-pictures-2011 and texlive-science-2001, possible also others, are depending on ruby. That, uh, should not happen. How *did* you install texlive? If you just emerged it, it should be in the WORLD set, and should not be removed by depclean. Also, I thought the new depclean nowadays would refuse to run if there are unresolved conflicts? I could also not find an accessible and up to date explanation of installing texlive. Set the correct USE flags (use 'equery uses texlive' or 'emerge --pretend --verbose texlive' to see the complete list. Select the ones you want/need). For example, on my box I have set in '/etc/portage/package.use' the following app-text/texlive dvi2tty extra games graphics humanities jadetex music omega pdfannotextractor pstricks publishers science tex4ht xetex -xindy And then just 'emerge texlive' should do the trick. Can any one guide me towards understanding how to proceed? I would rather not spend the next week re-installing my system. Perhaps I should back out of ~amd64 to amd64? Backing out of ~ is sometimes a non-trivial task, especially if it involves downgrading system packages like glibc. When I had to do it in the past, I had the luxury of time and so I 1) keyworded ALL currently installed version to x86 (or in your case amd64) 2) changed the make.conf setting to x86 (amd64 in your case). This way portage won't force you to downgrade anything that is installed and working, and after a month or two the stable keyword should catch up or surpass the testing keyword and you'll have a stable system again. W -- Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire et vice versa ~~~ I. Newton
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On 2011-12-13 5:42 PM, Leho Kraav l...@kraav.com wrote: i would first of all suggest dropping ssmtp and going with nullmailer. if ssmtp fails for any reason it will lose your emails. nullmailer has queue capability. Sounds good, I'll give it a shot (emerging now)... Is there a decent HowTo on getting it up and running? The manpage was full of technical stuff but I didn't see anmy clearcut examples of getting it actually running and being used as the systems default mta for sending messages. Thanks!
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On 2011-12-14 6:43 AM, Tanstaafl tansta...@libertytrek.org wrote:
On 2011-12-13 5:42 PM, Leho Kraav l...@kraav.com wrote:
i would first of all suggest dropping ssmtp and going with
nullmailer. if ssmtp fails for any reason it will lose your emails.
nullmailer has queue capability.
Sounds good, I'll give it a shot (emerging now)...
Ok, emerged, did emerge --config nullmailer, added:
# A nonstandard SMTP server setup:
# someotherserver.domain.com smtp --port=2525
mail.myserver.com smtp --port=587 --user=user --pass=pass
to /etc/nullmailer/remotes, and added it to default runlevel.
When starting manually I get the following warning:
li66-207 nullmailer # /etc/init.d/nullmailer start
* Starting nullmailer ... [ ok ]
* WARNING: -c/--chuid is deprecated and will be removed in the future,
please use -u/--user instead
li66-207 nullmailer #
Checking the init script, I see:
start() {
checkconfig
ebegin Starting nullmailer
cd /var/nullmailer
start-stop-daemon --start --quiet --chuid ${USER}:${GROUP} \
--exec ${DAEMON} -- ${ARGS}
eend $?
}
Should I change this? Ianap, so don't really feel comfortable just
changing it without confirming first...
Thanks again...
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On Dec 14, 2011 7:08 PM, Tanstaafl tansta...@libertytrek.org wrote:
On 2011-12-14 6:43 AM, Tanstaafl tansta...@libertytrek.org wrote:
On 2011-12-13 5:42 PM, Leho Kraav l...@kraav.com wrote:
i would first of all suggest dropping ssmtp and going with
nullmailer. if ssmtp fails for any reason it will lose your emails.
nullmailer has queue capability.
Sounds good, I'll give it a shot (emerging now)...
Ok, emerged, did emerge --config nullmailer, added:
# A nonstandard SMTP server setup:
# someotherserver.domain.com smtp --port=2525
mail.myserver.com smtp --port=587 --user=user --pass=pass
to /etc/nullmailer/remotes, and added it to default runlevel.
When starting manually I get the following warning:
li66-207 nullmailer # /etc/init.d/nullmailer start
* Starting nullmailer ... [ ok ]
* WARNING: -c/--chuid is deprecated and will be removed in the future,
please use -u/--user instead
li66-207 nullmailer #
Checking the init script, I see:
start() {
checkconfig
ebegin Starting nullmailer
cd /var/nullmailer
start-stop-daemon --start --quiet --chuid ${USER}:${GROUP} \
--exec ${DAEMON} -- ${ARGS}
eend $?
}
Should I change this? Ianap, so don't really feel comfortable just
changing it without confirming first...
Thanks again...
Don't.
Just file a bug, and let the maintainer take care of it.
It's *still* supported currently.
Rgds,
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On Wed, 14 Dec 2011 07:05:12 -0500, Tanstaafl wrote: When starting manually I get the following warning: li66-207 nullmailer # /etc/init.d/nullmailer start * Starting nullmailer ... [ ok ] * WARNING: -c/--chuid is deprecated and will be removed in the future, please use -u/--user instead Ignore it, it is only a deprecation warning. IMO these warnings shouldn't be displayed to normal users by default, they are intended for devs. -- Neil Bothwick Walk softly and carry a fully charged phazer. signature.asc Description: PGP signature
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On 2011-12-14 7:16 AM, Pandu Poluan pa...@poluan.info wrote: Should I change this? Ianap, so don't really feel comfortable just changing it without confirming first... Don't. Just file a bug, and let the maintainer take care of it. It's *still* supported currently. Will do... But, I noticed I was still getting the same error after unmerging ssmtp and emerging nullmailer, and /etc/ssmtp still exists... so apparently it is still trying to use ssmtp somehow? I moved the /etc/ssmtp dir (temporarily, until I figure this out) to my home directory, and set PORTAGE_ELOG_MAILURI= back to its default (commented it out), and now I'm getting this error: !!! A network error occurred while trying to send logmail: [Errno 111] Connection refused Sure you configured PORTAGE_ELOG_MAILURI correctly? How do I tell the system to use nullmailer?
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On Dec 14, 2011 7:22 PM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 14 Dec 2011 07:05:12 -0500, Tanstaafl wrote: When starting manually I get the following warning: li66-207 nullmailer # /etc/init.d/nullmailer start * Starting nullmailer ... [ ok ] * WARNING: -c/--chuid is deprecated and will be removed in the future, please use -u/--user instead Ignore it, it is only a deprecation warning. IMO these warnings shouldn't be displayed to normal users by default, they are intended for devs. ... or for normal users so that the normal users will file a bug. :-) Rgds,
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On 2011-12-14 7:25 AM, Tanstaafl tansta...@libertytrek.org wrote: !!! A network error occurred while trying to send logmail: [Errno 111] Connection refused Sure you configured PORTAGE_ELOG_MAILURI correctly? Ok, finally figured out why I wasn't seeing any errors in the main log... Here is the error in the main log: Dec 14 07:58:17 li66-207 nullmailer[27759]: Starting delivery: protocol: smtp host: mail.myserver.com file: 1323867377.8321 Dec 14 07:58:17 li66-207 nullmailer[13029]: smtp: Failed: 530 5.7.0 Must issue a STARTTLS command first Dec 14 07:58:17 li66-207 nullmailer[27759]: Sending failed: Permanent error in sending the message Dec 14 07:58:17 li66-207 nullmailer[27759]: Delivery complete, 1 message(s) remain. So... does nullmailer even support STARTTLS?
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On 2011-12-14 8:00 AM, Tanstaafl tansta...@libertytrek.org wrote: So... does nullmailer even support STARTTLS? Crap, apparently not... http://untroubled.org/nullmailer/TODO back to square one...
Re: [gentoo-user] What happened to OpenRC 0.9.6?
On 12/11/2011 1:10 PM, James Broadhead wrote: On 11 December 2011 10:41, Andrea Contia...@alyf.net wrote: On 27/11/11 16.36, Nikos Chantziaras wrote: sys-apps/openrc-0.9.6 is just... gone? Not even masked, but completely gone from portage. FYI, sys-apps/openrc-0.9.7 is out. Apparently, the solution to the rc_parallel issues was to remove every mention of rc_parallel from the default /etc/rc.conf Brilliant. I didn't take this email at face value when I read it earlier, but I just merged my openrc-0.9.7 config file. Wow, what a cynical move. Its only cynical in that it reflects a basic failing of human psychology, namely, thst warning doesn't apply to me syndrome. I imagine their thought process went something like this: We exposed this experimental feature that's hard to get right and only moderately useful, with explicit instructions not to complain if it doesn't work unless you are personally going to put in the time and effort to fix it. People blithely ignored our warning, enabled it, then complained loudly when it did not work. Since no one bothers to read the warning in rc.conf about this feature, and we have neither the time, manpower, nor overwhelming need to make it work, we'll just stop mentioning it. HOPEFULLY anyone smart enough to find and re-enable a hidden, explicitly unsupported feature will be smart enough not to complain when it doesn't work. --Mike
Re: [gentoo-user] Two issues with OpenRC/baselayout2 migration on a hosted VM
Pandu Poluan wrote, at 12/13/2011 10:26 PM: On Dec 14, 2011 1:06 AM, Tanstaafl tansta...@libertytrek.org mailto:tansta...@libertytrek.org wrote: What should I set this to? Assuming that Linode is indeed using Xen, would it be: rc_sys=xenU ? AFAIK Linode uses Xen so xenU is correct. What I really want to know is what happens if we specify a 'wrong' rc_sys value... (I also want to know why 'rc -S' is so unhelpful, but not as much as the above.) i have looked through openrc sources and experimented a bit; the idea of rc_sys is simple: the contents of that variable affects 'keyword' dependencies in /etc/init.d/ scripts. the feature is documented, see runscript(8) for details, but apparently does not work as expected. i also did not find valuable 'keyword' dependencies in software packages i use thus considered that rc_sys might be set to any value with no side effects another thing i found is an $RC_SYS environment variable available to all scripts initiated by rc; that one is set to value defined in /etc/rc.conf or automatically detected if rc_sys is not explicitly set. the automatic detection is trivial, eg. if the directory /proc/xen does exist, then $SYS_RC is set to XENU. setting of $SYS_RC to XEN0 would be in case of /proc/xen existence and if contents of the file /proc/xen/capabilities is equal to control-d. all that stuff could be found in src/librc/librc.c i'm using $RC_SYS as a flag controlling start of xen dom0 daemons: rc_sys is commented out in /etc/rc.conf to let runscript autodetect the environment. all xen related stuff is started from /etc/local.d, like that: $ cat /etc/local.d/xen.start if [ x$RC_SYS = xXEN0 ]; then # start xenstored, xenconsole, configure xen networking etc else # do something else related to baremetal os boot fi this slightly speeds up boot process and produces more clear logs
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On Wed, 14 Dec 2011 19:28:33 +0700, Pandu Poluan wrote: Ignore it, it is only a deprecation warning. IMO these warnings shouldn't be displayed to normal users by default, they are intended for devs. ... or for normal users so that the normal users will file a bug. :-) After they have asked about it on mailing lists and forums for the umpteenth time. The package devs and arch testers should see those messages, it's only a deprecation notice not an error. -- Neil Bothwick Windows - From the people who brought you EDLIN! signature.asc Description: PGP signature
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On 2011-12-14 8:05 AM, Tanstaafl tansta...@libertytrek.org wrote: On 2011-12-14 8:00 AM, Tanstaafl tansta...@libertytrek.org wrote: So... does nullmailer even support STARTTLS? Crap, apparently not... http://untroubled.org/nullmailer/TODO back to square one... Ok, found msmtp, which does support STARTTLS, and still can't get this working... I really hope I don't have to resort to installing postfix just to get simple outbound mail running... I've removed nullmailer (had to manually kill the still running process and delete the /etc/nullmailer dir for it too), and installed and configged msmtp, and it is still not working... I also did reset PORTAGE_ELOG_MAILURI= to default (commented it out). li66-207 ~ # msmtp --serverinfo SMTP server at smtp.myserver.com (smtp.myserver.com [70.43.81.99]), port 587: smtp.myserver.com ESMTP Postfix Capabilities: SIZE 3072: Maximum message size is 3072 bytes = 29.30 MiB PIPELINING: Support for command grouping for faster transmission ETRN: Support for RMQS (Remote Message Queue Starting) DSN: Support for Delivery Status Notifications STARTTLS: Support for TLS encryption via the STARTTLS command This server might advertise more or other capabilities when TLS is active. li66-207 ~ # So, it is talking successfully to my relayhost here in the office, but I'm still getting this ordinary error: !!! A network error occurred while trying to send logmail: [Errno 111] Connection refused Sure you configured PORTAGE_ELOG_MAILURI correctly? and NOTHING in/var/log/messages... Hope someone has an idea...
Re: [gentoo-user] Please ignore above email; I hit send by mistake
On 2011-12-14 07:32, Walter Dnes wrote: On Wed, Dec 14, 2011 at 01:12:10AM -0500, Walter Dnes wrote Please ignore the above email. I hit send by mistake. Long story short... the R200 is not supported under Mesa Gallium. So a glxgears rating of 262 fps with the ATI Radeon R200 card gives stuttering useless streaming video while the onboard Intel GPU is OK, even though it gives 60 fps under glxgears. Most likely you have vertical sync on for the onboard Intel gpu which can explain why you see it limited to 60 fps (lcds usually run at 60Hz). Best regards Peter K
Re: [gentoo-user] Who can tell me relationship among dri,glx,mesa,xorg?
2011/12/14 Lavender lavender_mat...@163.com Now I'm totally confused, I can't find helpful information from Internet. I know mesa is a open source implementation of OpenGL, obviously mesa will afford OpenGL API. DRI is short for Direct Rendering Infrastructure, I have chosen options like: Device Drivers --- Graphics support --- * Direct Rendering Manager --- *ATI Radeon [*] Enable modesetting on radeon by default Does this mean that DRI libraries are built into kernel? If not, who contains DRI? Also who affords GLX libraries? Mesa or Xorg? About Mesa: http://www.mesa3d.org/intro.html About DRI: http://dri.freedesktop.org/wiki/ -- Andrés Becerra Sandoval
Re: [gentoo-user] What happened to OpenRC 0.9.6?
Mike Edenfield wrote: On 12/11/2011 1:10 PM, James Broadhead wrote: On 11 December 2011 10:41, Andrea Contia...@alyf.net wrote: On 27/11/11 16.36, Nikos Chantziaras wrote: sys-apps/openrc-0.9.6 is just... gone? Not even masked, but completely gone from portage. FYI, sys-apps/openrc-0.9.7 is out. Apparently, the solution to the rc_parallel issues was to remove every mention of rc_parallel from the default /etc/rc.conf Brilliant. I didn't take this email at face value when I read it earlier, but I just merged my openrc-0.9.7 config file. Wow, what a cynical move. Its only cynical in that it reflects a basic failing of human psychology, namely, thst warning doesn't apply to me syndrome. I imagine their thought process went something like this: We exposed this experimental feature that's hard to get right and only moderately useful, with explicit instructions not to complain if it doesn't work unless you are personally going to put in the time and effort to fix it. People blithely ignored our warning, enabled it, then complained loudly when it did not work. Since no one bothers to read the warning in rc.conf about this feature, and we have neither the time, manpower, nor overwhelming need to make it work, we'll just stop mentioning it. HOPEFULLY anyone smart enough to find and re-enable a hidden, explicitly unsupported feature will be smart enough not to complain when it doesn't work. --Mike Sounds like good reasoning too. lol Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS=--quiet-build=n
Re: [gentoo-user] Who can tell me relationship among dri,glx,mesa,xorg?
Am Mittwoch, 14. Dezember 2011, 14:22:47 schrieb Lavender: Now I'm totally confused, I can't find helpful information from Internet. I know mesa is a open source implementation of OpenGL, obviously mesa will afford OpenGL API. DRI is short for Direct Rendering Infrastructure, I have chosen options like: Device Drivers --- Graphics support --- * Direct Rendering Manager --- this is DRM. This one manages allocation of memory for video devices. *ATI Radeon [*] Enable modesetting on radeon by default Does this mean that DRI libraries are built into kernel? No. If not, who contains DRI? Also who affords GLX libraries? Mesa or Xorg? DRI is part of mesa. Mesa also provides the GLX libraries. Best, Michael
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On 2011-12-14 10:29 AM, Tanstaafl tansta...@libertytrek.org wrote: !!! A network error occurred while trying to send logmail: [Errno 111] Connection refused Sure you configured PORTAGE_ELOG_MAILURI correctly? and NOTHING in/var/log/messages... Ok, so, I now have more info so hopefully some kind soul will take pity on me and provide the clue-stick... I can confirm that sending email from the commandline now works: li66-207 ~ # echo This is a test e-mail... | mail -s Test e-mail ad...@myserver.com li66-207 ~ # I received the email. But, I'm still getting the same error as above when portage tries to email me the emerge logs. How do I tell portage to simply use the 'mail' command?
[gentoo-user] Re: texlive 2011
Alan E. Davis lngndvs at gmail.com writes: I think texlive (is a pain in the ass) Numerous times over the years, I have had fits with texlive* Heres's my scratch notes the last time I figured out the issue was fonts (another time it was EVILution.(evolution). 1) equery b -f '/etc/texmf/.*' 2) Uninstalling all of the above reported ebuilds. 3) rm -rf /etc/texmf/* rm -rf /usr/share/texmf* emerge -C `qlist -I -C dev-texlive/*` 4) emerge -1 texlive YMMV. Basically, remove everything with textlive in the name as well as dependent packages (if all else fails) and check that it wants to install the version of textlive-* you need/want. Finding the actual culprit often burns many hours of hunt and seek... Ocationally I have to rebuild the system caveat emptor.. Good hunting, HTH, James
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On Wed, 14 Dec 2011 15:29:44 -0500 Tanstaafl tansta...@libertytrek.org wrote: On 2011-12-14 10:29 AM, Tanstaafl tansta...@libertytrek.org wrote: !!! A network error occurred while trying to send logmail: [Errno 111] Connection refused Sure you configured PORTAGE_ELOG_MAILURI correctly? and NOTHING in/var/log/messages... Ok, so, I now have more info so hopefully some kind soul will take pity on me and provide the clue-stick... I can confirm that sending email from the commandline now works: li66-207 ~ # echo This is a test e-mail... | mail -s Test e-mail ad...@myserver.com li66-207 ~ # Did you send this as user? What about sending this from the root account? Urs
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On 2011-12-14 3:59 PM, Urs Schutz u.sch...@bluewin.ch wrote: Did you send this as user? What about sending this from the root account? I sent it from root... maybe that's the problem?
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On Wed, 14 Dec 2011 15:29:44 -0500, Tanstaafl wrote: I can confirm that sending email from the commandline now works: How do I tell portage to simply use the 'mail' command? AFAIR there used to be an option for this, but it's not in the docs. Have you tried PORTAGE_ELOG_MAILURI=user@address localhost Or leave MAILURI unset in which case it will deliver to root@localhost. -- Neil Bothwick Top Oxymorons Number 4: Diet ice cream signature.asc Description: PGP signature
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On 2011-12-14 4:09 PM, Neil Bothwick n...@digimed.co.uk wrote: On Wed, 14 Dec 2011 15:29:44 -0500, Tanstaafl wrote: I can confirm that sending email from the commandline now works: How do I tell portage to simply use the 'mail' command? AFAIR there used to be an option for this, but it's not in the docs. Have you tried PORTAGE_ELOG_MAILURI=user@address localhost Or leave MAILURI unset in which case it will deliver to root@localhost. Yep, that's how it is set now... I'm stumped...
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
On Wed, 14 Dec 2011 15:29:44 -0500, Tanstaafl wrote: How do I tell portage to simply use the 'mail' command? You don't, you tell it to use sendmail From make.conf.example: mailserver: smtp server that should be used to deliver the mail (defaults to localhost) alternatively this can also be a the path to a sendmail binary if you don't want to use smtp Try PORTAGE_ELOG_MAILURI=you@home /usr/sbin/sendmail This will use ssmtp's sendmail, which you already have working. -- Neil Bothwick This is the day for firm decisions! Or is it? signature.asc Description: PGP signature
Re: [gentoo-user] Need help getting portage to email me emerge logs using ssmtp...
Neil Bothwick writes:
On Wed, 14 Dec 2011 15:29:44 -0500, Tanstaafl wrote:
I can confirm that sending email from the commandline now works:
How do I tell portage to simply use the 'mail' command?
AFAIR there used to be an option for this, but it's not in the docs.
Have you tried
PORTAGE_ELOG_MAILURI=user@address localhost
Or leave MAILURI unset in which case it will deliver to
root@localhost.
What about
PORTAGE_ELOG_COMMAND=cat '\${LOGFILE}' | mail -s 'ebuild log for
\${PACKAGE}' user@address
Doesn't seem to work here, though. Even if I set PORTAGE_ELOG_SYSTEM to
custom and PORTAGE_ELOG_COMMAND to an existing script, it is not being
called.
Wonko
Re: [gentoo-user] Re: texlive 2011
Once ruby was emerged, texlive installed pretty much without any MAJOR incident. On the #gentoo irc channel, the advice was received to unmask ruby 1.9. There seems to be some variation in how this is done, but that's basically all I needed to do. On Wed, Dec 14, 2011 at 12:57 PM, james wirel...@tampabay.rr.com wrote: Numerous times over the years, I have had fits with texlive* Luckily this is the first time I've installed texlive on this system. I've installed texlive from upstream source various times, without any major issue. It's a heck of a lot better than tetex used to be. Heres's m 1) equery b -f '/etc/texmf/.*' 2) Uninstalling all of the above reported ebuilds. 3) rm -rf /etc/texmf/* rm -rf /usr/share/texmf* emerge -C `qlist -I -C dev-texlive/*` 4) emerge -1 texlive Ocationally I have to rebuild the system caveat emptor.. I did find it difficult to figure out how to install texlive on Gentoo this time around, though. Seems a good howto is needed. This time around, I bascially just started emerging (emerge texlive) and after all the bumps and twists and turns, eventually I'd figured out that USE flags were needed. I hadn't seen that at first, even though I've installed texlive on Gentoo before, a couple or three years ago. Alan
[gentoo-user] DBI connect dbname=template1 failed Permission denied
I have postgresql up and running but when I try to connect via apache to
postgresql I get an error:
[error] [client 127.0.0.1] DBI connect('dbname=template1','sql-ledger',...) failed: could not connect to server: Permission denied, referer:
http://localhost/sql-ledger/admin.pl
Anybody knows what to look for?
--
Joseph
Re: [gentoo-user] DBI connect dbname=template1 failed Permission denied
On Dec 15, 2011 10:55 AM, Joseph syscon...@gmail.com wrote:
I have postgresql up and running but when I try to connect via apache to
postgresql I get an error:
[error] [client 127.0.0.1] DBI
connect('dbname=template1','sql-ledger',...) failed: could not connect to
server: Permission denied, referer: http://localhost/sql-ledger/admin.pl
Anybody knows what to look for?
--
Joseph
Check pg_hba.conf
Rgds,
Re: [gentoo-user] DBI connect dbname=template1 failed Permission denied
On 12/15/11 12:23, Pandu Poluan wrote:
On Dec 15, 2011 10:55 AM, Joseph syscon...@gmail.com wrote:
I have postgresql up and running but when I try to connect via apache to
postgresql I get an error:
[error] [client 127.0.0.1] DBI
connect('dbname=template1','sql-ledger',...) failed: could not connect to
server: Permission denied, referer: http://localhost/sql-ledger/admin.pl
Anybody knows what to look for?
--
Joseph
Check pg_hba.conf
Rgds,
I did, it is identical to my other working systems:
local all alltrust
here are other details:
# psql -p 5432 -U postgres
psql (9.1.1)
Type help for help.
postgres=#
Available PostgreSQL Slots
9.1 * server-9.1.1 base-9.1.1
--
Joseph
