I'd echo Dan here - * kill -9
* Running UniVerse cron jobs (especially as root) which are not PHANTOMs * ipcrm I have also sent the passwd file hand edited to copy entries and the user name changed for different users, however all have the same UID and GID. This can cause entertaining (but probably unwanted) effects when you force logout someone (whoops - there went everyone...). Similarly if you are not shutting UniVerse itself down cleanly? The other culprits are usually file system based: * Moving files in use * Changing permissions on files in use * Setting file exclusive locks on files which are in use (though you don't "lose" files with this, you ?just? get corruption. Unix level backups often the culprit when you don't stop UniVerse or use "SUSPEND.FILES ON". Regards JayJay ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
