I would suggest forking p9p and making get9root smarter ;) I will get to it some day...
That aside, yes, this seems like an annoying issue, specially if you want to setup werc in a shared hosting environment where you have no control over where you can install p9p. I would look if there is a way to make lighttpd set env variables for cgi scripts from its configuration files so you can set PLAN9 accordingly before calling werc. Another option is to hardcode your path in the source for get9root, it is a hideous hack, but should work (I think). Peace uriel On Wed, May 6, 2009 at 6:03 AM, sqweek <[email protected]> wrote: > > 2009/5/6 adam . <[email protected]>: >>> If all else fails, try #!/usr/bin/env PLAN9=/usr/share/plan9 >>> /usr/share/plan9/bin/rc >> tried that, no change. >> >> I did find the relevant error message from lighttpd I think: >> /usr/local/plan9/rcmain: rc (/usr/share/plan9/bin/rc): .: can't open: >> No such file or directory >> >> so something thinks rcmain is in /usr/local/plan9 for some reason? i'm >> a bit lost. > > Yes, rc does. It calls get9root() (source in > $PLAN9/src/lib9/get9root.c) which uses the PLAN9 environment variable > if it is defined, otherwise falls back on /usr/local/plan9. The env > trick works here: > > : nightingale ~/tmp; env PLAN9=/lol /usr/local/plan9/bin/rc > /lol/rcmain: rc (/usr/local/plan9/bin/rc): .: can't open: No such file > or directory > > Not sure what else to suggest. > -sqweek > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "werc" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/werc9?hl=en -~----------~----~----~----~------~----~------~--~---
