On Mon, 26 Sep 2016 13:52:55 -0300 Gustavo Sverzut Barbieri <barbi...@gmail.com> said:
> On Fri, Sep 23, 2016 at 11:39 PM, Carsten Haitzler <ras...@rasterman.com> > wrote: > > On Wed, 21 Sep 2016 23:47:15 -0300 Gustavo Sverzut Barbieri > > <barbi...@gmail.com> said: > >> >> looks good? > >> > > >> > no. no idle die. see above. :) it's portable. it's simple. it works > >> > everywhere until you have oddball smack/selinux etc. envs and then the > >> > env can take care of it via launch or socket actvation. first make the > >> > "works everywhere" version. :) > >> > >> it's almost done, the libproxy.so needs to fork-exec on errors... that's > >> it. > > > > why does it need to forke+exec on error? > > to spawn the daemon? > > error here = connect error, if that fails, spawn a new daemon oh the "connect to daemon failed" error. ok. i was thinking other errors like "proxy lookup failed" or "dns lookup failed" or whatever. :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
