I think you'd have to begin the lookups in the background as soon as the job
is parsed, and have a local cache of name to pwnam structure references. If
a lookup fails, you should have a mechanism to retry that lookup later (e.g.
when a network interface comes up).
At the point of starting a job, if the pwnam cache doesn't contain the name,
it should fail to start.
That's how I'd do it, anyway
Scott
On Wed, Apr 27, 2011 at 5:57 PM, goraxe <email address hidden> wrote:
I think you'd have to begin the lookups in the background as soon as the job
is parsed, and have a local cache of name to pwnam structure references. If
a lookup fails, you should have a mechanism to retry that lookup later (e.g.
when a network interface comes up).
At the point of starting a job, if the pwnam cache doesn't contain the name,
it should fail to start.
That's how I'd do it, anyway
Scott
On Wed, Apr 27, 2011 at 5:57 PM, goraxe <email address hidden> wrote:
> Any thoughts then on getting around the blocking nature of getpwnam? /code.launchpad .net/~goraxe/ upstart/ user_sid/ +merge/ 59309
> --
> https:/
> Your team Upstart Developers is subscribed to branch lp:upstart.
>