This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients gregory.p.smith, loewis, pitrou
Date 2011-01-26.10:41:17
SpamBayes Score 0.0029827605
Marked as misclassified No
Message-id <1296038478.44.0.445705009156.issue10826@psf.upfronthosting.co.za>
In-reply-to
Content
'D' denotes a door file. There are several of them in the system; the following ones (from /var/run) match the time stamp:

Dr--r--r--   1 daemon   daemon         0 Mar 27  2010 kcfd_door
Dr--r--r--   1 root     root           0 Mar 27  2010 name_service_door
Dr--r--r--   1 root     root           0 Mar 27  2010 picld_door
Drw-r--r--   1 root     root           0 Mar 27  2010 syslog_door

It's common for library routines to open a door and keep it open for the entire process lifetime.

If this was somehow reproducible, I could try to find out what specific door gets opened.
History
Date User Action Args
2011-01-26 10:41:18loewissetrecipients: + loewis, gregory.p.smith, pitrou
2011-01-26 10:41:18loewissetmessageid: <1296038478.44.0.445705009156.issue10826@psf.upfronthosting.co.za>
2011-01-26 10:41:17loewislinkissue10826 messages
2011-01-26 10:41:17loewiscreate