Re: [GENERAL] initdb error: "could not identify current directory"

hi joel, It looks to me like you are attempting to mount a few volumes under /var? actually, no. i'm symlinking local volumes mounted where they're supposed to be, in /Volumes, to ny /var/sub-hierarchy. I think that's going to wrinkle your handkerchief in Darwin. it's all been settled, actually (

Re: [GENERAL] initdb error: "could not identify current directory" (or,

> % cd /var/data/pgsql (B> still reports the absolute path (B> --> /Volumes/data/pgsql (B (BIt looks to me like you are attempting to mount a few volumes under /var? (B (BI think that's going to wrinkle your handkerchief in Darwin. (B (B-- (BJoel Rees <[EMAIL PROTECTED]> (Bdigitcom, inc

Re: [SOLVED] Re: [GENERAL] initdb error: "could not identify current directory" (or, what have i done now?)

OpenMacNews <[EMAIL PROTECTED]> writes: > whoa! i wasn't suggesting that at all ... rather, perhaps, simply a perms > check > from within the initdb script and an 'informative' error to the > end-user. We're doing the best we can already: when the failure occurs, we really don't know which direc

Re: [SOLVED] Re: [GENERAL] initdb error: "could not identify current directory" (or, what have i done now?)

OpenMacNews <[EMAIL PROTECTED]> writes: > on my sys: >% ls -ald /Volumes/data > drwxr-x--x 12 openmac wheel 408 Nov 27 15:25 /Volumes/data/ Ah-hah, yes that's undoubtedly it. > if this *does* turn out to be the case, does it make sense to have the script > check perms up through the

[SOLVED] Re: [GENERAL] initdb error: "could not identify current directory" (or, what have i done now?)

hi tom, i think i got it ... keeping in mind your question re: read perms, & reading this thread: and noting

Re: [GENERAL] initdb error: "could not identify current directory" (or,

hi tom, per this thread, i've been googl'ing on 'getcwd initdb permissions parent' and find lots of refs ... issues with folks having 'permission denied' errors if parent directories don't have correct permissions, etc. this 'smells' pretty much like the issue at hand here ... tho' i dunno (yet)

Re: [GENERAL] initdb error: "could not identify current directory" (or,

hi tom, % ls -ald /Volumes/data/pgsql drwxrwxr-x 12 testuser testuser 408 Nov 25 09:12 /Volumes/data/pgsql Huh? Why didn't the rm -rf remove both of those? Or are you skipping some steps? oops, sorry, copy-n-paste-itis: % rm -rf /var/data/pgsql/* /Volumes/data/pgsql/* % cd /var/data/pg

Re: [GENERAL] initdb error: "could not identify current directory" (or, what have i done now?)

OpenMacNews <[EMAIL PROTECTED]> writes: > then, i stumbled across the following behavior.: > % rm -rf /var/data/pgsql /Volumes/data/pgsql > % ls -ald /var/data/pgsql > lrwxr-xr-x 1 root wheel 27 Nov 22 20:26 /var/data/pgsql -> > /Volumes/data/pgsql > % ls -ald /Volumes/data/pgsql >

Re: [GENERAL] initdb error: "could not identify current directory" (or,

hi there, % /usr/local/pgsql/bin/initdb --pgdata=/var/data/pgsql --username=testuser could not identify current directory: Permission denied What directory are you in when you give this command? (AFAIR su doesn't change directory ... you might be better off with su - testuser ...) h, that'

Re: [GENERAL] initdb error: "could not identify current directory" (or, what have i done now?)

OpenMacNews <[EMAIL PROTECTED]> writes: >> su testuser > % /usr/local/pgsql/bin/initdb --pgdata=/var/data/pgsql --username=testuser > could not identify current directory: Permission denied What directory are you in when you give this command? (AFAIR su doesn't change directory ... you might

[GENERAL] initdb error: "could not identify current directory" (or, what have i done now?)

hi all, i just clean-rebuilt pgsql8b5 os OSX 10.3.6 the build went fine as before -- no errors reported. per instruction, i've created an unpriv'd user: testuser. now, however, when i try to 'initdb', creating in '/var/data/pgsql': su testuser % /usr/local/pgsql/bin/initdb --pgdata=/var/data/pgsql