When you are testing the functionality of a DAS client, it is helpful to have a checklist. This is especially
important when you are testing a new GNU/Linux distribution or Unix OS with the DAS. Use the checklist to make sure that
it is configured correctly and working properly.
Given an existing DAS user (e.g. "kitty"), you should test the following four scenarios:
- Both DAS servers are available/reachable
- DAS-S is unavailable, DAS-M is available
- DAS-M is unavailable, DAS-S is available
- Neither DAS-M nor DAS-S are available
For the last two scenarios, consider stopping the nscd service.
- Can a locally defined user login?
- Can "root" login?
- Will the host boot up correctly?
- DAS user (user) login at console (good + bad passwords)
- User login via SSH
- User login via gFTP with SFTP
- User login through GDM or equivalent (graphical login screen)
- Screensaver unlock by user (GUI environment)
- User changes password with kpasswd
- Local root user su - kitty, attempts to change kitty's password
- getent test
- ypcat test and other yp commands
- Send e-mail between DAS users, between non-DAS users, and between DAS and non-DAS users (same host)
- As the root user, do the following:
- id kitty
- ls -al /home
- finger, who, w
- attempt to useradd "on top of" an existing DAS user
- attempt to usermod an existing DAS user
- ps -aux, top
- cron jobs and at jobs for DAS users
- check quota support for DAS users, including the use of repquota, quota, setquota, and edquota
You may also want to test the following items with DAS users:
- Test with and without firewall/packetfilter enabled
- DAS user account expiration
- POSIX ACLs with DAS users
- Automatic creation of home directories for DAS users (when enabled)
- SSO programs like Kerberized rlogin, rsh, rcp, ftp, telnet - connect to an app server