| View previous topic :: View next topic |
| Author |
Message |
pstruh
Voice
Joined: 04 Mar 2005
Posts: 11
|
 Posted: Thu May 11, 2006 6:34 am Post subject: Tcl error [tv]: couldn't execute "php": no such fi |
 |
|
Hi I have problem with tcl script.
If I try to use command etc. !tv in eggdrop party line displayed me:
Tcl error [tv]: couldn't execute "php": no such file or directory
Cau you help me fix it?
thanks |
|
| Back to top |
|
 |
De Kus
Revered One
Joined: 15 Dec 2002
Posts: 1361
Location: Germany
|
| Posted: Thu May 11, 2006 7:33 am Post subject: |
|
|
have you read the install instructions? I am sure you are missing a php command line tool within the search path or something like that.
_________________
De Kus
StarZ|De_Kus, De_Kus or DeKus on IRC
Copyright © 2005-2009 by De Kus - published under The MIT License
Love hurts, love strengthens... |
|
| Back to top |
|
|
pstruh
Voice
Joined: 04 Mar 2005
Posts: 11
|
| Posted: Thu May 11, 2006 7:58 am Post subject: |
|
|
| De Kus wrote: | | have you read the install instructions? I am sure you are missing a php command line tool within the search path or something like that. |
Problem is, in few days ago all working perfect, no error messages, but If I reboot server then this error was alert.
lines of script
set script_home "/home/cha/eggdrop/scripts"
set results [split [exec php $script_home/tvprog.php "$arg"] "\n"] |
|
| Back to top |
|
|
dwickie
Halfop
Joined: 21 Aug 2004
Posts: 76
Location: /pub/beer
|
| Posted: Thu May 11, 2006 10:49 am Post subject: |
|
|
| try replace "php" in [exec php $script_home/tvprog.php "$arg"] with full path (eg. /usr/bin/php) |
|
| Back to top |
|
|
pstruh
Voice
Joined: 04 Mar 2005
Posts: 11
|
| Posted: Thu May 11, 2006 2:45 pm Post subject: |
|
|
| dwickie wrote: | | try replace "php" in [exec php $script_home/tvprog.php "$arg"] with full path (eg. /usr/bin/php) |
Yes, Now its working perfect 
thanks man |
|
| Back to top |
|
|
De Kus
Revered One
Joined: 15 Dec 2002
Posts: 1361
Location: Germany
|
| Posted: Fri May 12, 2006 4:57 am Post subject: |
|
|
you alternately should be able to solve by adding /usr/bin to export PATH in ~/.bash_profile. Type 'export | grep PATH' to see current paths. A healthy PATH should contain at least "/usr/local/bin:/usr/bin:/bin"; /sbin, /usr/sbin, /usr/local/sbin and ~/bin might also be a good choice, if avaible.
_________________
De Kus
StarZ|De_Kus, De_Kus or DeKus on IRC
Copyright © 2005-2009 by De Kus - published under The MIT License
Love hurts, love strengthens... |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
