I need some help hopefully someone else has run into this or at least dealt with the EMC lifeline apps (now retired) but in general here is the issue:NAS device is booting I've done a bunch of iSCSI tuning and everything else with the addition of the iscsid-scst.conf file that didn't even exist, I can now confirm with the iscsi-scst-adm --op show --tid=1 --sid=0 that all my params are good EXCEPT TWO:MaxRecvDataSegmentLengthMaxXmitDataSegmentLengthWell, as it turns out after a ton of reverse engineering already how this NAS operates, all the new settings hold and despite these two also being defined, they are simply being overridden by the scst.conf file that looks like this:# Generated by Lifeline iSCSI module.HANDLER vdisk_fileio{    DEVICE VMware {        filename /mnt/pools/A/A0/iSCSI/VMware        t10_dev_id LENOVO-b3fbe43e        usn b3fbe43e        nv_cache 1    }}TARGET_DRIVER iscsi {    iSNSServer 192.168.1.6    enabled 1    TARGET iqn.2012-07.com.lenovoemc:storage.ix2b.VMware {        MaxRecvDataSegmentLength 8192        MaxXmitDataSegmentLength 8192        enabled 1        LUN 0 VMware    }}Well that top line is LITERAL, because that module is totally regenerating this and my changes are simply overridden (even edited only the comment line which was reset).All my work is really killed by these two params being strapped to this tiny # when I need them set to 262144.I've been grepping and digging and just can't find what code is responsible for rewriting this conf file at boot.Can anyone help?  TIA!
EMC Lifeline iSCSI module on NAS regenerating scst.conf every boot
nas;iscsi