Inconsistent permissions on shell command about shell2http HOT 9 CLOSED

For posterity, here are the details of the snap isolation rules:

https://snapcraft.io/docs/snap-confinement
https://snapcraft.io/docs/permission-requests

Installing from snap with --devmode option also solves the permission issue by giving the program full access to systems resources.

from shell2http.

Do you definitely run both commands (shell2http and tail) under the same user?
tail and tail under shell2http should work the same, i checked it now.

Maybe try copying the log-file to the current directory and run tail logfile.log, what will be happened?

from shell2http.

Yes, both command were executed by the root user.

Copying the file to the current directory and running tail logfile.log is working with or without the "x" permission in the parent folders.

The tail command inside shell2http -port=80 / "tail /many/folders/logfile.log" is working only if all parent folders of logfile.log have the "x" permission, regardless of the logfile being moved up or down some directories.

from shell2http.

not reproducing, tail has the same behavior under shell2http and without

from shell2http.

Something very weird is going on...

shell2http is the snap version

shell2http/shell2http is compiled from source (git clone and go build)
Same result with go get

from shell2http.

Oh, yes, applications from snap packages have their own sandbox which provides many limitations, for example restrict access to the host filesystem.

from shell2http.

Nothing can be done here, with snap shell2http. Please use deb-package or binary from github releases or build from source.

from shell2http.

I would never thought of that. Now that I know what the issue is, I'm starting to find some problems related to that while searching.
Compiling the program myself definitely solves the issue for me.

Thanks for your help, greatly appreciated.

from shell2http.

You're welcome

from shell2http.