On 8/5/2014 18:50, Sean Woods wrote:
I saw that jimsh references glob.tcl, so I removed all my local Tcl/Tk
stuff -- I wasn't really using it -- and rebuilt Fossil clean from tip,
to force it to use jimsh, and it still doesn't happen.
How did you do this? My knowledge of the TCL ecosystem isn't that
great.
I tugged on loose bits of yarn until the sweater unraveled. It didn't
all come to me in a blinding flash of revelation.
it's trying to stat `/home` which on my system has restricted
access (not readable or writable by "others").
Do you realize that *you* are one of those "others" in this context?
Your stat(1) output says all you've done is "chmod 711 /home" relative
to the stock CentOS 5 /home permissions, which are 755 root.root. Since
you are neither root nor a member of group root, the only reason you can
even cd into your own home directory is the o+x permission. "chmod 710
/home" would lock you out of the system entirely.
I suggest that you add yourself to the stock "users" group, then log out
and back in again, then "chgrp users /home && chmod 750 /home".
An even better solution to "others" crawling around in /home is SELinux.
Not that any of this actually solves the problem. I chmodded my CentOS
5 box's /home to 711, too, and Fossil still builds. The real problem is
this glob.tcl file, which isn't present on my system, anywhere. Why you
have one is a complete mystery to me. You're seeing jimsh0 reading it,
then complaining when it hits line 13 in that file.
I see two ways to fix it:
1. Find this glob.tcl file, and move it out of the way, at least
temporarily.
2. Install tcl to get tclsh, and forget about jimsh0's confusion.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
