Re: What happens to the AppKit Framework when an user logout ?
Re: What happens to the AppKit Framework when an user logout ?
- Subject: Re: What happens to the AppKit Framework when an user logout ?
- From: Will Price <email@hidden>
- Date: Tue, 16 Oct 2001 18:13:21 -0700
It seems to me that the answer must be more complex than that. We are
having problems with this very same issue.
We need to have a background service which presents GUI at times. This
background service is not specific to any user, it is specific to the
machine. It is a startup item. So, we have for instance something like
"service.app" which runs as root at startup time using the plist
background service marker (we've tried LSBackgroundOnly=1 and
NSUIElement=1, neither solve this problem though they do work in the
simple case).
In any case, everything works great until a user logs out. When a user
logs out, anything with a CFRunLoop appears to get killed. So far, we
haven't found a solution to this other than completely removing anything
that uses AppKit/Foundation from all background services which effectively
renders useless the concept of Cocoa background services.
Any suggestions? Conceptually, we're thinking that perhaps if we removed
our connection to the Window Server from the runloop set when a user logs
out, we might not get killed? In any case, this is a critical issue for
us.
Ali Ozer wrote:
>
> My current guess is that the AppKit Framework is unloaded during the
>
> logout. Is it correct ?
>
>
"unloading" is more of a 9 concept, I think. On X, frameworks will get
>
paged out automatically when they are not being used. There is no
>
explicit "unloading" event. Of course it turns out that even when you
>
are logged out, the AppKit can still be used; loginwindow itself uses it
>
for instance.
>
>
So the answer is --- nothing special happens to the AppKit framework
>
when the user logs out.
>
>
Ali
--
Will Price, Director of Engineering
PGP Security, Inc.
a division of Network Associates, Inc.