[jira] [Commented] (CLOUDSTACK-6220) Cloudstack agent fails to start due to broken init script

["Marcus Sorensen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13926238#comment-13926238 ] 

Marcus Sorensen commented on CLOUDSTACK-6220:
---------------------------------------------

commit 9dd57c22b02afcddb1d6c8ddc3e1b578961454e3
Author: John Kinsella <jl...@stratosec.co>
Date:   Mon Feb 17 10:00:36 2014 -0800

    CLOUDSTACK-6129: removing hard-coded script names
    
    Replacing whatami with $0 which is how UNIX shell scripts should get the
    script's name.
    
    BUG-ID: CLOUDSTACK-6129
    Bugfix-for:
    Reviewed-by:
    Reported-by:
    Signed-off-by: John Kinsella <jl...@stratosec.co> 1392660036 -0800


> Cloudstack agent fails to start due to broken init script
> ---------------------------------------------------------
>
>                 Key: CLOUDSTACK-6220
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6220
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Install and Setup
>    Affects Versions: 4.4.0
>         Environment: CentOS 6.5 KVM/libvirt
>            Reporter: Nux
>              Labels: agent
>
> Hello,
> On 4.4 `service cloudstack-agent start` fails with:
> # service cloudstack-agent start
> Starting Cloud Agent: 
> touch: cannot touch `/var/lock/subsys//etc/init.d/cloudstack-agent': No such file or directory
> /etc/init.d/cloudstack-agent used to have this which worked fine:
> whatami=cloudstack-agent
> SHORTNAME="$whatami"
> Now it has been replaced with this which fails:
> SHORTNAME="$0"
> A possible solution is to replace "$0" with `basename "$0"`



--
This message was sent by Atlassian JIRA
(v6.2#6252)