Glad it's working for you!
A significant reduction in complexity. However, and the reason for my
delay in replying. Magic happened! I was now transmitting data which
crossed jail barriers (from b3 "named" to b2 "named logging"). I needed
to consult with one of the FreeBSD developers to
On 4/10/2020 1:14 pm, Laurent Bercot wrote:
>> 1. I expected to see the date in seconds since time epoch, but result is
>> variable name
>> # execlineb -Pc 'backtick D { date "+%s" } echo $D'
>> $D
>
> Normal behaviour, since there's no shell to interpret $D as the
> contents of variable D. Try
Apologies, my earlier email, item 2, pointed to emptyenv as the cause of
zombie processes on FreeBSD 12.2S, actually it is due to background.
Ah, then everything is working as intended and there's no anomaly.
background spawns a process as a direct child, so if the parent execs
into a
1. I expected to see the date in seconds since time epoch, but result is
variable name
# execlineb -Pc 'backtick D { date "+%s" } echo $D'
$D
Normal behaviour, since there's no shell to interpret $D as the
contents of variable D. Try using "importas D D" before the echo:
it will read the value
Apologies, my earlier email, item 2, pointed to emptyenv as the cause of
zombie processes on FreeBSD 12.2S, actually it is due to background.
# execlineb -Pc 'background { echo hello } pipeline { ps -axw } grep
defunct'
hello
30144 0 Z+ 0:00.00
while the following tests both foreground
Is this correct behaviour or are these just anomalies?
1. Use of backtick variable assignment on FreeBSD doesn't appear correct
2. Use of emptyenv results in a remnant "defunct" process
3. Should a bundle's contents file include the dependencies of its
contents file, for a down change to the
