• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Detecting login/logout?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Detecting login/logout?


  • Subject: Re: Detecting login/logout?
  • From: Stéphane Sudre <email@hidden>
  • Date: Sat, 1 Nov 2003 11:25:15 +0100

On samedi, novembre 1, 2003, at 05:46 AM, Wade Tregaskis wrote:

(2) Programs that are launched via the StartupItems mechanism are in a different Mach bootstrap context than normal processes. When the user logs in, your program will be killed, because it has created Mach ports (by linking and using certain CoreFoundation functions) and those ports will be stale when the new Mach context is brought > forward.

Are you sure the existing context is destroyed? How do normal programs (e.g. system daemons) survive? I was under the impression that you just couldn't communicate (with mach ports) between login processes and user processes.

As soon as your software is "connected" to the Window Server, your application will die at logout. So the idea is to use the APIs which are WindowServer safe and to use a bootstrap daemon.

For instance, you can use CoreFoundation APIs, CoreCarbon, but NOT Carbon.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.
  • Prev by Date: Re: Detecting login/logout?
  • Next by Date: Re: modifying protected file
  • Previous by thread: Re: Detecting login/logout?
  • Next by thread: Re: Detecting login/logout?
  • Index(es):
    • Date
    • Thread