A couple of things that might be the issue, or at least reasonable guesses.
1. Something in readin  is trying to access a resource that does not exist
on this machine
2. permissions are set wrong on readin (needs to be x  etc)
3. Something like ACL rules were set on readin
https://tylersguides.com/guides/linux-acl-permissions-tutorial/

On Mon, Oct 5, 2020 at 5:09 PM joe--- via PLUG-discuss <
plug-discuss@lists.phxlinux.org> wrote:

> In my /home/joe/bin directory, I have hundreds of
> shell scripts that I use for various utilities.
>
> Recently, thanks to advice from Matt Graham, I added these
> lines to .bashrc which got most of those utilities to work:
>
> export PATH=/home/joe/path:$PATH
>
> However, one of the files in /home/joe/bin is a proprietary
> binary file named 'readin' that functions like a "hot key"
>
> It works fine on my other Linux boxes, but since I copied my
> entire 'bin' directory onto another Linux machine, I can't
> get 'readin' to work on this machine.
>
> In fact, it cannot even be "found" even though it is certainly
> there in /home/joe/bin ... but when I type readin at the command
> line, I get this message:
>
> joe@drifter:~/bin$ /home/joe/bin/readin
> bash: /home/joe/bin/readin: No such file or directory
>
> Hope someone can explain why 'readin' is not found
> when it is actually there.
> ---------------------------------------------------
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> https://lists.phxlinux.org/mailman/listinfo/plug-discuss