Hello all, i can see a lot of issues where we try to use tools from new/custom PATH.
all problems have beed found by DilOS - where we have another tools in /usr/bin /sbin etc. they are problems are not visible on original illumos env like OI - what is using for zfs tests. right now, by step in zfstest - we do symbolic links to tempory directory and update PATH to use it. but - we are using 'su user -c "<cmd line>" - where we use another PATH - it is not the same as we defined. as example: zfs-tests/tests/functional/acl/cifs/cifs_attr_001_pos it use 'su' in some places where we use 'chmod' from another location - it is not the same what we linked to temporary PATH. it is one example what we can’t trust to linked tools to temporary directory with PATH. we have a lot of another scenarios where we can use another tools from another locations and tests can produce incorrect resuts. based on these issues i’d like to start activity again to use full static path to tools like CHMOD=/usr/bin/chmod - where we can be 100% sure we are using what we want to use. current zfs tests define tools by symbolic links to temporary directory and try to use it by providing PATH, but we can’t trust to this PATH and time to time we are using tools from another location - it is not good and we can’t trust to results. bets regards, -Igor ------------------------------------------ openzfs: openzfs-developer Permalink: https://openzfs.topicbox.com/groups/developer/T73c62864791e915c-Me235f18572779a4eda36edde Delivery options: https://openzfs.topicbox.com/groups
