On RHEL3, FAM is installed by default, so I didn't install anything in this regard. I don't see any fam processes running by default, but a process called fam (owned by the first user to login) seems to be started by KDE(?) at login time. I guess this is not the correct approach? I have rebuilt KDE3.2.3, two days before 3.3 appeared :(, with libfam disabled, which seems to avoid the problem. As most of our storage is on remote NetApp filers, I guess there is little benefit in using FAM anyway? (I'm guessing NetApp filers don't have remote FAM support) Thanks, Nick. On Wed, 2004-08-18 at 09:12, James Richard Tyrer wrote: > Nick THOMPSON wrote: > > I have multiple users unable to login, due to what looks old fam > > processes left running. Sometimes killing fam sorts this out, but I have > > three instances now, where the user can't login, or the login is very > > very slow (several minutes) and I can't fill fam. > > > > Any ideas how I can get the users going and maybe avoid using fam in > > future? > > My best guess is that you have some sort of a configuration problem. > > How did you install: FAM and Xinetd? ___________________________________________________ . Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.