Note that with SETUID and root ownership, rdxport.cgi is (if my Linux semantics are correct) running as root, not the RD user. This is probably not what you want, although it is a brute-force solution to your problem (at the expense of considerable security). If it's not working when owned by the RD user, it's probably because there is a permission error elsewhere where the RD user should have some access rights but does not. By running it as root, you have access to everything, so your solution is masking the underlying issue.
It's been a while since I setup a new Rivendell system from scratch, but I don't think you should need (or want) to run rdxport as root. Maybe some of the others on this list know which files might have the wrong permissions that are keeping you from running it as the RD user? -Andy Sayler On Thu, Nov 3, 2011 at 10:56, Keith Thelen <[email protected]> wrote: > Problem appears to be solved. > > The wiki says: "rdxport.cgi should be SETUID (mode 4755) and likewise > owned by the Rivendell system user and group." > Turns out that's halfway correct in my case - it did need to be setuid, > but needed to be owned by root. > > chown root:root rdxport.cgi > chmod 4755 rdxport.cgi > > and the problem would appear to be no more. > > > > --------------- > Keith Thelen > Kanabec Systems > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
