On Thu, Feb 28, 2008 at 7:14 AM, Ben K. <[EMAIL PROTECTED]> wrote: > > Yes, a restart is required for extensions to work. They would have > > Thanks for the reply Dan. How would I restart a shared server ... is > that something I can do from the command line? Or do I just have to wait > it out until it automatically restarts?
It is probably started as a fcgi process, since its on a shared host? Then, just change the timestamp on public/dispatch.fcgi: $ touch path/to/dispatch.fcgi The fcgi process will restart as soon as it noticess the change, practically imediatelly. You could also send a message to the process to kill itself explicitely with a (s)kill command: $ skill -9 <PID> (same for the kill command). PID stands for process id. Use the "ps" command to find out the PID of the fcgi process: $ ps ux Or you could kill them all: $ skill -9 dispatch.fcgi (won't work for "kill" command) Or you could just wait for it to reastart automatically. :) Sorry, this is written for total beginners, I'm not sure how good is your "command line fu". _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
