On Mon, 15 Oct 2012 20:07:28 -0700 Dave Ray <ap...@jonive.com> said:

> Hi,
> 
> On Oct 15, 2012, at 8:45 AM, Carsten Haitzler (The Rasterman) wrote:
> 
> > On Mon, 15 Oct 2012 07:31:04 -0700 Dave Ray <ap...@jonive.com> said:
> > 
> >> Hi,
> >> Yes, it exists. But there may be something wrong with the full path e17 is
> >> looking for:
> >> $ ls
> >> -al /var/folders/p9/p447lsgn76z04gn3hdvlzgs40000gn/T/enlightenment-davidray
> >> \@0000000000000000/ total 0 drwx------  3 davidray  davidray  102 Oct 15
> >> 07:19 . drwx------  4 davidray  davidray  136 Oct 15 07:25 ..
> >> srwxrwxrwx  1 davidray  davidray    0 Oct 15 07:19 disp-:0.0-1743%F0??
> >> $
> >> 
> > %F0?? ... almost looks like something became corrupt. the path buffer is
> > limtied to 1024 bytes but your path is much less than that. the code
> > literally is:
> > 
> >                  snprintf(buf3, sizeof(buf3), "%s/disp-%s-%i",
> >                           buf, disp, pid);
> > so u have buf and disp output find but pid has junk appended to it and
> > snprintf sure as hell doesnt append that. oooh wait...
> > 
> > ecore_con will APPEND "|%i" to it:
> > 
> >               snprintf(buf,
> >                        sizeof(buf),
> >                        "%s|%i",
> >                        svr->name,
> >                        svr->port);
> > 
> > does osx disallow '|' in file paths?
> 
> Yes, OSX does allow '|' (pipe symbol) in file paths. A shell interpreter is
> likely to fail with a pipe in the filename though.
> 
> I tried this a few more times. The socket file e17 creates is always a
> mismatch with the file that the console message say it's looking for. I guess
> this is why the file menus aren't working.
> 
> When the console error is:
> Cannot connect to enlightenment (socket
> '/var/folders/p9/p447lsgn76z04gn3hdvlzgs40000gn/T//enlightenment-davidray@0000000000000000/disp-:0.0-8629
> 
> The socket file created is:
> disp-:0.0-8629%EC??
> 
> I don't understand how
> snprintf(buf,sizeof(buf),"%s|%i",svr->name,svr->port); 
> can end up as 
> %EA??
> 
> So the part of the filename appended by ecore_con is totally broken on OSX. 

since it seems to be a socket path limitation (in size) and you've used a long
XDG_RUNTIME_DIR, TMPDIR or SD_USER_SOCKETS_DIR just to make it worse... :)
i've shortened the other bits of the socket name to make it hopefully fit in -
but if you make any of these env vars longer yet still u'll hit the problem
again. i suggest finding a way to keep them ... short :)

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to