On RHEL, it should be /etc/init.d/ for sure, and you manage the startup scripts with /sbin/sysconfig
-jk On Tue, Aug 31, 2010 at 8:38 AM, Mattias Jiderhamn < mj-li...@expertsystems.se> wrote: > We are on RedHat Enterprise Linux 4/5. > > Note that the question is not the configuration itself, but *where* is the > proper place for such configuration. The file we use now is overwritten with > "the one which ships with Resin" on every Resin update. > > </Mattias> > > jkowall wrote (2010-08-31 14:19): > > Depends on the version of Unix you are on exactly. I customized the init > script quite a bit, so I don't use the one which ships with Resin. Which > version/distribution are you using? I can share the one I use if you'd > like. > > -jk > > > On Tue, Aug 31, 2010 at 4:10 AM, Mattias Jiderhamn < > mj-li...@expertsystems.se> wrote: > >> (I am not by far a *nix wizz, nor the admin of our production servers, >> so please bear with me) >> >> Historically we have edited the /etc/init.d/resin script to customize >> the Resin startup, such as setting the server root directory or >> assigning CPU cores with taskdef. >> In the 4.0.x branch this file is overwritten at each minor upgrade by >> "make install". Does this mean this is (no longer) the recommended way >> of configuring the startup, and there is some other means we should look >> at instead...? >> >> -- >> >> </Mattias> > > > > _______________________________________________ > resin-interest mailing list > resin-interest@caucho.com > http://maillist.caucho.com/mailman/listinfo/resin-interest > >
_______________________________________________ resin-interest mailing list resin-interest@caucho.com http://maillist.caucho.com/mailman/listinfo/resin-interest
