Package: runit
Version: 2.1.2-35
Followup-For: Bug #943397
Dmitry Bogatov wrote:
> Can you please elaborate on this case? How could runsv(1) know whether
> "run" file was read or not?
I've probably put in a way that is misleading: I don't know how/if runsv
knows whether run file was read.
You
[2019-11-13 14:35] Lorenzo Puliti
> >Are you sure about "wrong sh syntax" part?
>
> You are right, this is very inaccurate. Just for the records, I've
> made some tests :
> [...]
>
> * invoke-run exits before executing run's file code --> exit -1
Can you please elaborate on this case? How
Package: runit
Version: 2.1.2-35
Followup-For: Bug #943397
[Thu, 07 Nov 2019 00:30:45] Dmitry Bogatov
>> +echo "runsv: ERROR $1 in $NAME: unexpected error or wrong sh
>> syntax"
>>
>
>Are you sure about "wrong sh syntax" part?
You are right, this is very inaccurate. Just for
[2019-11-06 13:45] Lorenzo Puliti
> Package: runit
> Version: 2.1.2-35
> Followup-For: Bug #943397
>
> I'm attaching two patches for review;
> one thing that I'm still not sure about is the exit code range. $1 in
> the finish file can be run's exit code or the daemon's exit code. I'm
> using
Package: runit
Version: 2.1.2-35
Followup-For: Bug #943397
I'm attaching two patches for review;
one thing that I'm still not sure about is the exit code range.
$1 in the finish file can be run's exit code or the daemon's exit code.
I'm using the wierd range 160-170 but is still possible that the
[2019-10-24 14:34] Lorenzo Puliti
> Package: runit
> Version: 2.1.2-35
> Severity: normal
>
> As discussed in #934231
>
> [Dmitry Bogatov]
> >> create mode 100644 debian/anacron.runscript/finish
>
> > There is nothing in this script specific to anacron. I propose
> > following:
> > []
>
>
Package: runit
Version: 2.1.2-35
Severity: normal
As discussed in #934231
[Dmitry Bogatov]
>> create mode 100644 debian/anacron.runscript/finish
> There is nothing in this script specific to anacron. I propose
> following:
>
> * add this finish script into bin:runit as
7 matches
Mail list logo
