All users have read/write permissions on those files, so this doesn’t make sense (to me) from a Unix permissions standpoint.
I am indeed a BSD guy, but ... in reality fossil is running in a docker container on a Linux server and accessing the files via sshfs mount. I can futz about and make the UIDs match, but unless fossil itself is making decisions based on UID I don’t understand the point. I haven’t looked at the code and understand fossil may be dropping permissions at some point, but the fossil binary is running as the root user in this case. > On Dec 20, 2017, at 5:54 PM, Warren Young <war...@etr-usa.com> wrote: > >> On Dec 20, 2017, at 3:40 PM, dewey.hyl...@gmail.com wrote: >> >> # ls -lh /fossils|grep fossil >> -rw-rw-rw- 1 1000 root 272.0K Dec 19 14:37 archsetup.fossil >> -rw-rw-rw- 1 1000 root 224.0K Dec 19 14:36 >> guac-install-script.fossil >> -rw-rw-rw- 1 1000 root 224.0K Dec 19 14:37 miscreports.fossil >> -rw-rw-rw- 1 1000 root 304.0K Dec 19 14:37 pkgReport.fossil > > # chown -R arealuser /fossils > > User 1000 doesn’t exist on your system, so those files are unreadable by > Fossil, which isn’t running as root. > > Bonus guess: you scp’d or rsync’d this over to a BSD box from a Linux box > with permission preservation, where the Linux box starts normal users at UID > 1000 and the BSD box starts at 500. > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
