Re: (Fwd) Re: includes inside squid.conf

Question:

Why don't we just use a "helper" thats totally not related to squid
at all, and use say, sockets, or named pipes, or _something_
and then have some generic mechanism to communicate this into squid?

That way, we're not forking a huge process, we don't need to worry about
nasty things happening (since squid won't die - our helper app will)..

2c,

Adrian

On Wed, Apr 03, 2002, Henrik Nordstrom wrote:
> Issues:
>
> a) We need to clean up not only filedescriptors but also drop root
> privileges etc before starting the child.. with vfork this can only
> be done with a intermediary helper.. exec to intermediarey helper who
> cleans up things and then execs the real thing.
>
> b) Some UNIX:es have given up on providing a correct vfork() and have
> it identical to fork(), making it somewhat counter-productive to
> spend time today on making correct use of vfork().
>
> c) Things crash an burn if the child receives a signal between
> vfork() and execve().
>
> d) There is no directly clean way to handle a failed execve() when
> vfork() is used.
>
> Remains to see if we even can use posix_spawn for Squid (haven't
> actually read about it yet, but preleminary it looks good..)
>
> For now we will stick to plain fork().
>
> Regards
> Henrik
Received on Wed Apr 03 2002 - 02:41:03 MST