Forum: Ruby on Rails Spawner -p and --port not working?

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Sean H. (Guest)
on 2006-01-23 23:46
(Received via mailing list)
Hi everyone,

I'm trying to set a port with spawner, and it's not working:

ruby /var/rails/ldapadmin/current/script/process/spinner -c
/var/rails/ldapadmin/current/script/process/spawner --port=7000 -i 4
-d
spinner: invalid option: --port=7000

Same with -p:

ruby /var/rails/ldapadmin/current/script/process/spinner -c
/var/rails/ldapadmin/current/script/process/spawner -p 7000 -i 4 -d
spinner: invalid option: -p 7000

And then it just keeps spawning lots of fcgi processes that die
because the default port is already taken by another app on the
machine.

Why isn't the port piece working?

Thanks,

Sean
Sean H. (Guest)
on 2006-01-24 23:23
(Received via mailing list)
Nevermind on this.  Lighttpd wasn't running.  I still hadn't separated
lighttpd and fcgi in my head.  Lighty should be on, and SwitchTower
handles the fcgi processes, period.  I think.

Sean
This topic is locked and can not be replied to.