Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Permissions too restrictive on single socket

#107

When a single thin is started with the --socket option:

thin --socket /tmp/app1.thin.sock start
>> Using rails adapter
>> Thin web server (v1.2.2 codename I Find Your Lack of Sauce Disturbing)
>> Maximum connections set to 1024
>> Listening on /tmp/app1.thin.sock, CTRL+C to stop

The permissions on the socket are too restrictive to allow others to talk to it:

ls -la /tmp/app1.thin.sock
srwxr-xr-x 1 mina mina 0 Aug 10 14:47 /tmp/app1.thin.sock

Since nginx is not running as "mina", I need to manually relax the socket's permissions with chmod every time (give "w"rite to world).

Interestingly, thin started with multiple servers via --servers doesn't have this problem.

Reported by Mina Naguib · August 10th, 2009 @ 02:50 PM

State: new
Milestone: Future
Assigned to: macournoyer macournoyer

Activity

  1. macournoyer
    macournoyer

    If you daemonize the process (-d option) it should work to.

    Why don't you daemonize it?

    August 10th, 2009 @ 10:07 PM

  2. Mina Naguib
    Mina Naguib

    No reason, other that it wasn't part of usual flow (GNU screen/window 0=web server/easy restart via ctrl+c,up,enter)

    --daemonize appears to work. Thanks for the tip.

    Took me a while to figure it out though. If it's a trivial fix I think it might be worth addressing.

    August 10th, 2009 @ 11:24 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.