Greg Wooledge wrote:
read out < <(declare -p "$var")
----
That code actually isn't called. It's used by "isarray" to tell me whether
or not a var is an array.
The code that doesn't work is the line with the comment "line 233".
(which is now line 235 from the latest error message.
<notice -- Jul 22 19:02:49.388388000> service boot.clock start
assign_netif_names=/etc/init.d/boot.assign_netif_names start
ifname=eth0, hwaddr=00:15:17:bf:be:b2
ifname=eth1, hwaddr=00:15:17:bf:be:b3
ifname=eth2, hwaddr=00:26:b9:48:71:e2
ifname=eth3, hwaddr=00:26:b9:48:71:e4k
ifname=eth4, hwaddr=a0:36:9f:15:c9:c0
ifname=eth5, hwaddr=a0:36:9f:15:c9:c2
/etc/init.d/boot.assign_netif_names: line 235: act_hw2if: bad array
subscript
/etc/init.d/boot.assign_netif_names: line 235: act_hw2if: bad array
subscript
/etc/init.d/boot.assign_netif_names: line 235: act_hw2if: bad array
subscript
/etc/init.d/boot.assign_netif_names: line 235: act_hw2if: bad array
subscript
/etc/init.d/boot.assign_netif_names: line 235: act_hw2if: bad array
subscript
/etc/init.d/boot.assign_netif_names: line 235: act_hw2if: bad array
subscript
Note that according to the "printf in "read_actuals", the values are
correctly
being read in from my "here var".
Note, you can't use an assignment there.
It's reading names+hwaddrs of the net devs @ boot
in "get_net_IFnames_hwaddrs". That requires line and field
splitting.
Now that I'm writing about it -- I'm thinking that
it doesn't like me using the hwaddr's @ boot time as hash subscripts.
That's what I don't understand. It works "normally", but
why would "hashes" fail at boot? I couldn't think of how they'd
be implemented to use some non-existent service, so I don't
know which resource lack is causing the fail.
I won't even try to guess why she can't just do out=$var ... there is
probably some extremely silly reason that will just make me want to slam
my head into my desk....
---
Yeah, like multiple lines and fields in "$var"...
