how do you kill a user's old processes when they try to log back on

[Todd O'Bryan]

Actually, Firefox v3 has been pretty wonky for other reasons. It's really
slow and does weird things, even on my desktop machine, so I had considered
uninstalling it and going back to v2.

On the other hand, it looks like from Asmo's email that the change to avoid
stressing thin clients isn't on by default, so I'll try setting that and see
if it helps any. That doesn't solve the problem with OpenOffice, though,
which does the same kind of pixmap caching, with the same disastrous
results, so XRAMPERC is kind of necessary until we get OO worked out, too.

Todd

On Mon, Sep 1, 2008 at 6:09 AM, Gavin McCullagh <gmccullagh at gmail.com>wrote:

> On Fri, 29 Aug 2008, Todd O'Bryan wrote:
>
> > As a follow-on to this question, is the XRAMPERC variable that was
> available
> > in Gutsy still available in Hardy? I added a setting to
> > /var/lib/tftpboot/ltsp/i386/lts.conf, but users could still crash their
> > terminals by going to a particularly graphics heavy website in Firefox.
>
> I'm not sure about XRAMPERC to be honest, but it's disappointing to hear
> firefox crashed a client as, if that's firefox v3, it should have the new
> code in it to reduce the stress it puts on the X server (which caused it to
> crash).
>
> Are you using firefox v3, yeah?
>
> Gavin
>
>
> --
> edubuntu-users mailing list
> edubuntu-users at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/edubuntu-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/edubuntu-users/attachments/20080901/f50f99a3/attachment-0001.htm