Artemis administration
From Space Science Theory Group
Contents |
Setting up users
Create the user
Regular users on artemis should be created in the LDAP directory so that mail works for them. Here's how:
- Run
# yast2 users &
- Set filter to "LDAP users". You will need the LDAP admin password (the LDAP admin by the way is "cn=Manager,dn=artemis,dn=sr,dn=unh,dn=edu"), which is stored in /etc/openldap/slapd.conf (SSHA hashed) and the same as the root pw at this time.
- Add the user. In assigning the uid, we shall try to follow the following convention:
- Jimmy Raeder's group: Use 4000's
- Amitava Bhattacharjee's group: Use 5000's
- Ben Chandran: Use 6000's
Note: After a bit of digging, I found out that in order for the above to create the user's home directory, one needs to check the FileServer setting in yast's LDAP section. Works now...
DON'T: Alternatively, on the command line:
artemis:~ # useradd -D 'cn=manager,dc=artemis,dc=sr,dc=unh,dc=edu' --service ldap \
-u 4002 -m jdorelli
Another note: That's not such a good idea!!!, since useradd will create the entry as "account", not "inetOrgPerson", which makes it difficult to add other (addressbook) data later.
Create the user's mailbox
- Run the imap server's config tool: (The password is again the same as usual...)
artemis:~ # cyradm -u cyradm localhost Password:
- Create the mailbox
localhost> cm user.<username>
Finalize the user
After generating a new user with the yast2 tool, you must also do the following:
# admin/user_update.sh <username>
The script expects the login name, not the user UID.
User management notes
Getting the usual user management commands (passwd, useradd, userdel, usermod, etc to work with LDAP users is a bit tricky and inconsistent (not to say, SuSE is kinda buggy).
- To change a user's password as root, one can now use the normal passwd <user>.
- For everything else, one needs to add -D cn=Manager,dc=artemis,dc=sr,dc=unh,dc=edu to the command line,
- useradd additionally needs --service ldap to make it do the desired thing.
Things to do after a crash
Keep in mind that you should read these notes prior to a crash, since you will be unable to read when you really need them ;-)
If the wiki's and email are down, it is possible that mysql needs to be revived. As root:
# rcmysql status Checking for service MySQL: running
If it is not running, do a
# rcmysql start
You may also want to tail the /var/log/messages to gain insight into why the machine died. Other favorites may include a tail of /var/log/mail.info or /var/log/warn

