UPDATE: Nov 29, 2007
For those of you who use the user postgres, to run a locally compiled version of your postgres database,
you will find out, that in the latest solaris 10, you cannot ssh in, nor telnet in as postgres.
I solved this, read below (the goodies are at the bottom)
If you are like me, you probably always download the latest postgres release, put the tarball in /usr/local/downloads/
then you make sure you copy /bin/bash , into /sbin/bash (so that the root acct still works in single user mode)
and you change the /etc/passwd file, so that root has /sbin/bash as a shell.
You can then have a /.bash_profile with the following crap inside:
PATH=/usr/local/bin:/usr/ccs/bin:/usr/sfw/bin:/usr/local/pgsql/bin:/usr/sbin:/usr/bin
LD_LIBRARY_PATH=/usr/local/lib:/usr/local/pgsql/lib:/lib:/usr/lib:/usr/sfw/lib
export PATH LD_LIBRARY_PATH
then you goto download-ftp-center.com, and download the latest readline source package.
untar your readline, change into the folder, and do the ubiquitous ./configure ; make ; make install
then you do the same thing for the postgres tarball
So, once both are installed, you want to use the user postgres, to "initdb -E LATIN1 /raidbox1/postgres824" (or something like this)
however, since you will be sending database dumps and backups in and out of the box,
and since the new solaris 10 does not allow you to log in as user postgres from an external box,
you find yourself chucking your lunch break, as you try to fuck around with ssh configs, etc etc, to no avail,
Ergo, after 5 hours, you find out the user "postgres" has been bastardized into a non-working crap stupid preconfigged shit account.
this is what I did to solve our little problem:
1. take out the group "postgres", from /etc/group
2. add the user postgres after a comma , in the /etc/group file, under the group called "other"
your line will read:
other::1:root,postgres
3. you modify the postgres entry in /etc/passwd to contain:
postgres:x:100:1:PostgreSQL:/data1:/sbin/bash
(or any other home folder you want, I always found /home/postgres rather crappy and cheesy, sounds like a Microshit invention)
4. you give it a password
as root, type: passwd postgres
and you type it in twice (make sure the password is something that , if a hacker guesses it, calls him a loser haha)
5. then you create its home folder, and make sure its chown -R postgres /da_homeola_foldage , chgrp -R other /da_homeola_foldage
6. You edit the new evil evil file called: /etc/user_attr
and you comment out the postgres entry, my line reads now:
#postgres::::type=role;profiles=Postgres Administration,All
7. VOILLA, you can now ssh in as postgres, and telnet in as postgres, and you are able to use the machine as a nice server cluster slave again.
And once again, we beat the BOFH who are working 24/7 on funky ingenious ways to fuck our lives
(like the idiot who killed our precious "used to be unhackable" telnet.)