| 1 |
On Tuesday 26 April 2005 23:20, Grob Team wrote: |
| 2 |
> When trying to start postgresql (run_init /etc/init.d/postgre start) |
| 3 |
|
| 4 |
There is no such thing as postgre. There is no such init script called |
| 5 |
postgre either. If there is in some obscure place, it certainly has nothing |
| 6 |
to do with the PostgreSQL database. |
| 7 |
|
| 8 |
> I got the "Starting PostGreSql" and nothing after, |
| 9 |
|
| 10 |
No you didn't. There's no capital G in PostgreSQL, nor lower case 'ql' unless |
| 11 |
you type every letter as lower case. Calling it Postgres or PostgreSQL or |
| 12 |
postgres or postgresql is fine, but that's about it. The init scripts are |
| 13 |
correct, so I'm sure you did not get a message that said the above. |
| 14 |
|
| 15 |
Sorry to be pedantic, but it really annoys me when people call something by a |
| 16 |
wrong name. |
| 17 |
|
| 18 |
> So, I tried to do: so - postgres and it "freeze" too. So maybe its not |
| 19 |
> postgres but a problem with pam/su. |
| 20 |
|
| 21 |
You're right in that it's not a problem with Postgres. Try tailing the system |
| 22 |
log (/var/log/everything/current if you use metalog) while attempting to su |
| 23 |
and see. Also |
| 24 |
|
| 25 |
> However, postgres is a valid user |
| 26 |
> # cat /etc/passwd | grep postgres |
| 27 |
> postgres:x:70:70::/var/lib/postgresql:/bin/false |
| 28 |
|
| 29 |
Try 'pwunconv && pwconv' to rebuild your shadow file. If that doesn't help |
| 30 |
then it's beyond me and somewhere in the bowels of pam. |
| 31 |
|
| 32 |
Good luck, |
| 33 |
-- |
| 34 |
Casey Allen Shobe | SeattleServer, Inc. |
| 35 |
cshobe@×××××××××××××.com | cell 425-443-4653 |
| 36 |
http://www.seattleserver.com |
| 37 |
-- |
| 38 |
gentoo-hardened@g.o mailing list |
Archives