• 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
daemon-child dies on user lougout
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

daemon-child dies on user lougout


  • Subject: daemon-child dies on user lougout
  • From: Mario Emmenlauer <email@hidden>
  • Date: Tue, 07 Oct 2008 14:21:25 +0200


Hi,

I'm picking up on a thread called 'launchd daemon, spawning children?'.

Terry Lambert wrote:
On Oct 1, 2008, at 3:40 AM, Mario Emmenlauer wrote:
One last question: If "worker_user" is the current GUI-user, all his
applications get killed on logout. Is there a way around this (or would
using 'login' also solve this issue?)

The logout operation for non-GUI applications sends either a SIGHUP (the correct signal), or a SIGTERM (not the correct signal). You can ignore or catch these signals with a signal handler, although if you ignore SIGTERM, you will delay shutdowns.


In general, daemons running as that user are not kiplled unless they are in the process group, or their parent is the per-session launchd. Otherwise, you would not be able to ssh into a machine and log out of a GUI and not have it kill your ssh (which it doesn't do).

Seems only logical. But I have an odd behavior there, my application dies on user-logout. Here is the scenario:

 - daemon is running as root
 - daemon fork()s a child, that setuid()s to some user
 - child exec()s some worker program
 - worker connects on a socket to the daemon, using ICE (www.zeroc.com)
 - if the worker runs as current GUI user, and that user logs out, the
   worker dies/crashes.
 - if the worker runs as any other system user, all works fine.


ReportCrash saves a report similar to the one attached. The only thing my child and server are doing are the network connection, and some disk usage. When I use a dummy worker that does nothing (sleeps), it doesn't die (and gets no SIGTERM or SIGHUP sent, as Terry already predicted).

So I can only imagine that the logout kills the ICE socket connection for
that user? Does that make any sense to anyone?

Cheers,

   Mario

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: daemon-child dies on user lougout
      • From: Terry Lambert <email@hidden>
References: 
 >Re: launchd daemon, spawning children? (From: Mario Emmenlauer <email@hidden>)
 >Re: launchd daemon, spawning children? (From: Terry Lambert <email@hidden>)

  • Prev by Date: Re: impossible constraint in asm
  • Next by Date: Re: Fwd: errno global vx. errno pthread...
  • Previous by thread: Re: launchd daemon, spawning children?
  • Next by thread: Re: daemon-child dies on user lougout
  • Index(es):
    • Date
    • Thread