On Fri, Sep 2, 2011 at 5:13 AM, John Robson <[email protected]> wrote: > I create a script in: $ /etc/init.d/wt > > #! /bin/sh > > ### BEGIN INIT INFO > # Provides: wt [...] > Add using: # update-rc.d wt defaults > > And Every time I start my server... Automatically UP all Wt Sites > (wthttp OK).
Yes, this is more or less what I meant. The only "but" I would pose to your approach is IMHO it's better to have one init script per wthttp application. That way you can easily stop/reboot one of them, have different start paremeters, create appropriate directories for each one without polluting the init script too much, etc > Apache... > > I create '/run/wt' just ONE time: > > $ mkdir /srv/www/run/wt; > $ sudo chown www-data:www-data /srv/www/run/wt -R; > > Apache2 start in boot and all my Wt Apache Sites its working too (wtfcgi > OK). Are you sure that's working fine? The Filesystem Hierarchy Standard (not the Linux Standard Base as I said before, sorry) mandates that /var/run (now moved to /run) be completely cleaned on boot. -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
