I personally use my application binary to start the postmaster, that way
I can check for the existance of the postmaster window before deleting
any files, and I can also start the postmaster as a console app attached
to the main dialog (or document view), and hide/unhide it as I please.I
also create the pg_hba.conf/etc files at run-time, and delete them once
the postmaster has started, in order to create a little bit more
security. Has anyone else run into the problem of having the backend run
in an untrusted environment on win9x machines (ie. no user protections
on the file system)? I've managed to whittle the install down to the
point where it's barely usable by anything but my app, but I can't
prevent someone from taking the data home, modifying it, and bringing it
back the next day...or re-installing the whole cygwin environment and
having a field day...any suggestions on locking it down?
-Brian Marshall
PS: No, I don't have the option of running the PCs on W2K etc, or having
a seperate unix box for the back end ^_^;
>
> In order to reliably start up the postmaster, I have been using a script
> to wrap around the postmaster binary and clean up some files that might
> otherwise prevent the postmaster from starting.
>
> The script looks something like this:
>
> #!/usr/bin/bash
> PGDATA=/usr/local/pgsql/data
> rm -f $PGDATA/postmaster.pid
> rm -f /tmp/.s.PGSQL.5432.lock /tmp/.s.PGSQL.5432
> exec /bin/postmaster
>
> This improved reliability 8 months ago.
>
> Does anyone else use/need something like this? Or do the newer versions
> simply work better without this functionality?
>
> Mike Adler
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>