I thought about the privileged status and opted to try to use /usr/sbin/pmount tonight and it’s doing the same thing. Back to square one. > On Jun 11, 2018, at 5:22 PM, Ryan Coleman <RYAN.COLEMAN at CWIS.BIZ> wrote: > > The thing that’s confused the ~!@# out of me was that it worked a couple of times and then stopped working, even in the sporadic manner. > > I’ll be looking at it again tonight. > >> On Jun 9, 2018, at 9:41 AM, Iznogoud <iznogoud at nobelware.com> wrote: >> >>> >>> Your concern is noted but not applicable. This truly is no different than mounting a drive automatically on a desktop. >>> >> >> Yup. I figured you know what you are doing, but I thought I'd bring it up. >> Sounds like a sandboxed machine with a specific purpose. >> >> >>> I’ll look at permissions but I don’t know quite where that would be at. >> >> This is a tough one. "mount" can only be executed by privileged accounts, in >> general. Can you try the following to see if the error is coming from mount >> and not from the tools? Instead of mount execute something like: >> echo "DID IT" > /tmp/attempt_text >> Completion should be successful; if it is not, you have a starting point. >> Then, you will see the owner of the newly created file, which, if it does >> exist, immediately tells you that mount returns an error, most likely related >> to permissions. >> >> I hope this helps. >> >> _______________________________________________ >> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota >> tclug-list at mn-linux.org >> http://mailman.mn-linux.org/mailman/listinfo/tclug-list > > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list