On Mon, Feb 16, 2015 at 5:08 PM, Buck Evan <[email protected]> wrote: > There's no dependant service involved. > > My check is running from outside the docker, racing against runit. > > Your workaround is valid, but still a workaround. My patch obviates the need > for the workaround. > Workaround or no, your patch changes the behavior of `sv check' to differ from the rest of the sv command set. Running `sv check' against any non-supervised directory, of which a not-yet supervised directory is a subset, should be, and is, a terminal event. This holds true for any of the sv commands, not just check. -- "If the doors of perception were cleansed every thing would appear to man as it is, infinite. For man has closed himself up, till he sees all things thru' narrow chinks of his cavern." -- William Blake
- patch: sv check should wait when svrun is not ready Buck Evan
- Re: patch: sv check should wait when svrun is not ready Crest
- Re: patch: sv check should wait when svrun is not ready Buck Evan
- Re: patch: sv check should wait when svrun is not rea... Colin Booth
- Re: patch: sv check should wait when svrun is not... Avery Payne
- Re: patch: sv check should wait when svrun is not... Buck Evan
- Re: patch: sv check should wait when svrun is... Colin Booth
- Re: patch: sv check should wait when svrun is... Avery Payne
- Re: patch: sv check should wait when svr... Buck Evan
- Re: patch: sv check should wait when... Avery Payne
- Re: patch: sv check should wait ... Buck Evan
- Re: patch: sv check should wait ... Buck Evan
- Re: patch: sv check should wait ... Avery Payne
- RE: patch: sv check should wait ... James Byrne
- runit maintenance - Re: patch: s... Gerrit Pape
- Re: runit maintenance - Re: patc... Buck Evan
