[
https://issues.apache.org/jira/browse/COUCHDB-1055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12990151#comment-12990151
]
Adam Kocoloski commented on COUCHDB-1055:
-----------------------------------------
Yes, the following works:
#! /usr/bin/env sh
Maybe you clear up something about that invocation for me. I get that env is
used to make sure we invoke the sh command specified by the user's environment,
but is it some sort of POSIX specification that "env" itself is always located
in /usr/bin?
> Timing-related failures in 172-os-daemon-errors.t
> -------------------------------------------------
>
> Key: COUCHDB-1055
> URL: https://issues.apache.org/jira/browse/COUCHDB-1055
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 1.2
> Reporter: Adam Kocoloski
> Assignee: Paul Joseph Davis
> Priority: Minor
> Fix For: 1.2
>
>
> I see quite a few of these on Hudson. Here's one that happened when the
> daemon simply does init:stop(). It seems to happen more often when the
> server is executing two jobs at once.
> # Daemon dies on boot.
> ok 8 - Daemon port is a port.
> ok 9 - Daemon name was set correctly.
> ok 10 - Command name was set correctly.
> ok 11 - Kill command was set.
> not ok 12 - Daemon has been halted.
> ---
> description: "Daemon has been halted."
> found: running
> wanted: halted
> ...
> not ok 13 - Errors have been disabled.
> ---
> description: "Errors have been disabled."
> found: [{1296,674759,844395}]
> wanted: nil
> ...
> not ok 14 - Buffer has been switched off.
> ---
> description: "Buffer has been switched off."
> found: []
> wanted: nil
> ...
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
