How then are you supposed to go about upgrading Resin? Is there a parameter to the "configure" script to avoid creating/overwriting /etc/init.d/resin?
If not, could such parameter be added...?


jkowall wrote (2010-08-31 14:45):
On RHEL, it should be /etc/init.d/ for sure, and you manage the startup scripts with /sbin/sysconfig


On Tue, Aug 31, 2010 at 8:38 AM, Mattias Jiderhamn < <>> 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.


    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.


    On Tue, Aug 31, 2010 at 4:10 AM, Mattias Jiderhamn
    < <>> wrote:

        (I am not by far a *nix wizz, nor the admin of our production
        so please bear with me)

        Historically we have edited the /etc/init.d/resin script to
        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...?



resin-interest mailing list

Reply via email to