http://bugzilla.suse.com/show_bug.cgi?id=906900 Thomas Blume <thomas.blume@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(max@suse.com) --- Comment #44 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Reinhard Max from comment #42)

All in all, if writing a unit file is the only way to get around the login session problem of pam_unix, the way to go is probably to move just the user switching from the init script to the unit file. IOW, the unit file would be moved out of /etc/init.d and the su stuff would be removed from it, then the unit file would take care of switching to the postgresql user and just call the init script.

Ok, this is also possible. (In reply to Bernhard Wiedemann from comment #43)

...

is there a scriptable (I know it can be done in C) way to acchieve the side effects of "su -" without creating a new login session?

If plain "su" and sudo do not do what you want, it can probably be done with env (1)

According to Werner, env wouldn't help. I will provide a service file that just runs the init script as postgres user. This, however, requires that all commands in the init script can run with the permissions of the postgres user. Reinhard, can you confirm this? -- You are receiving this mail because: You are on the CC list for the bug.