Killall command?


#1

I think I need to issue a killall command to my shared server so that database changes are applied within my Ruby on Rails app. I’ve added a new user to my Rails app’s table manually and I am unable to log in with the account.

I have tried using

But I get a message telling me no processes were killed…

What do I need to do to get this to work?


#2

Why not try a manual kill command with the Process ID. Granted, if that process isn’t showing up in ‘top’ or ‘ps’ then you’re not going to be able to kill it.

-Scott


#3

How would I find out what processes are running?

I also read somewhere that Dreamhost have disabled users’ ability to issue killall commands… does anyone know if this is true?


#4

I just gave you two commands that will list your processes.

-Scott


#5

Why don’t you move your app to Passenger? It runs much better than cranky old FCGI. In Passenger, all you have to do to restart an app is create a restart.txt file:

touch ~/YOUR_APP/tmp/restart.txt

The file gets deleted as soon as Rails has restarted.

Chances are you’re already on Passenger without knowing it. That would explain why no FCGI process got killed.

Oh, and AFAIK you don’t need to restart Rails to apply a database change, only if you changed something in Rails controllers or models. If your database changes are not reflected, maybe it’s a caching issue?