Turbo Fredriksson

Is there any more news on this? I'm using "EC2 Image Builder" to build an image, I've enabled the `stig-build-linux-high/2.8.0` component (which basically does the CIS hardening on the image)...

Logfiles from the first (successful) and the second (failed) boot: [i-0d8c83f3351c1a2ca-boot1.log](https://github.com/anthcourtney/ansible-role-cis-amazon-linux/files/5603833/i-0d8c83f3351c1a2ca-boot1.log) [i-0d8c83f3351c1a2ca-boot2.log](https://github.com/anthcourtney/ansible-role-cis-amazon-linux/files/5603834/i-0d8c83f3351c1a2ca-boot2.log)

Just an update before I take weekend - it's *SOMETHING* (!!) to do with the mounts. Not sure which one yet, but commenting out all but the root fs and...

It seems the Amazon Linux 2 AMI I use as base mounts EFS/NFS mounts to early in the boot process, messing up the rest of it. So the solution was...

Yes, I saw that. But that, on the other hand, is suppressing ALL message about this in the whole file. And many of them are valid. Just not those two...

… or in the whole function (didn't notice the first comment part - nice touch!).

Unfortunately, I honestly don't know what I expect that you do about this… In the function example, the call to $CMD SHOULD be quoted, but not the args. But if...

POSSIBLY (just spit-balling here), the comment directive in your example could be extended to ignore a variable? Like: ``` my_function() { local PIDFILE="$1" ; shift local CMD="$1" ; shift local...

… and extending that to multiple variables: ``` # shellcheck disable=SC2059:PIDFILE;VAR1;VAR2;[etc],SC2001:VAR19 ```

That is both a bashism and a "Assigning an array to a string"… ``` my_function() { local PIDFILE="$1" ; shift local CMD="$1" ; shift local ARGS=("$@") "$CMD" -p "$PIDFILE" "$ARGS"...