Thin stop acts funny with Swiftiplied servers

Activity

Carl
I found out why it's happening. The PID files are owned by my current user instead of the user I specified in my configuration file. The user in the config file has lower privileges.
If I chown the PID files to my "web" user, Thin can stop just fine.

April 20th, 2008 @ 02:18 PM
macournoyer
- Milestone set to 0.8.2
- State changed from new to resolved
The pid file is created before changing the user and stopping doesn't change the current user.
Probably you started it the first time w/ another user.
Let me know if you think this is an issue in thin.

April 20th, 2008 @ 08:06 PM
Carl
I think it's an issue that should be fixed quite frankly. As a user, I expect "stop" to stop the servers and not give me a bunch of errors because of the internals.
You could easily change the ownership of the PID files after they're created. That'd solve the problem.

April 20th, 2008 @ 11:19 PM
macournoyer
It's the same thing as if you
```
sudo touch something.txt
```
You won't be able to
```
rm something.txt
```
You need to start and stop w/ the same user like you do w/ any web server, apache, nginx, mongrel.
And what do you mean by internals? The backtrace?
April 21st, 2008 @ 10:02 AM

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.