[jira] Commented: (TS-199) Startup script should fail on "multiple" invocations of "start" (or "stop")

["Jason Giedymin (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844203#action_12844203 ] 

Jason Giedymin commented on TS-199:
-----------------------------------

many standard inits do not report [fail] but I think it should.  I've done this with nginx.
The file "TS-199-v3-JasonGiedymin.patch" does correct reporting and also has a nice pid wait.

> Startup script should fail on "multiple" invocations of "start" (or "stop")
> ---------------------------------------------------------------------------
>
>                 Key: TS-199
>                 URL: https://issues.apache.org/jira/browse/TS-199
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: Packaging
>            Reporter: Leif Hedstrom
>            Priority: Minor
>         Attachments: TS-199-v2-JasonGiedymin.patch, TS-199-v3-JasonGiedymin.patch, TS-199_r1.patch
>
>
> If I do
> # /etc/init.d/trafficserver start
> # /etc/init.d/trafficserver start
> I'd expect the second invocation to give an error, [NO]. Same thing with stop, if I run stop multiple times, if there are no process(es) to stop, each invocation ought to generate errors as well, e.g.
> root@loki 507/0 # ./local/bin/trafficserver stop
> Stopping :                                                 [  OK  ]
> Stopping :                                                 [  OK  ]
> Stopping :                                                 [  OK  ]
> root@loki 508/0 # ./local/bin/trafficserver stop
> Stopping :                                                 [  NOT  ]
> Stopping :                                                 [  NOT  ]
> Stopping :                                                 [  NOT  ]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.