Hi, Tekki:

The system scripts are not shell scripts, so I don't know how to set the 
variables…

The error log  from syslog says:
Apr 13 18:28:17 foo tiendas_admin: Can't load application from file 
"/media/psf/w/tiendas/tiendas_admin/script/tiendas_admin": *Can't find 
application class* *"TiendasAdmin"* *in* *@INC. (lib 
*/home/tester/perl5/perlbrew/perls/perl-5.20.1/lib/site_perl/5.20.1/x86_64-linux
 
/home/tester/perl5/perlbrew/perls/perl-5.20.1/lib/site_perl/5.20.1 
/home/tester/perl5/perlbrew/perls/perl-5.20.1/lib/5.20.1/x86_64-linux 
/home/tester/perl5/perlbrew/perls/perl-5.20.1/lib/5.20.1 .)

If I run hypnotoad from the user *tester* shell, everything runs fine, 
because those variables are activated when the shell is opened. But how can 
I do that from user *root* or when rebooting the system if I am nor 
executing a bash script?

Thanks:
Nacho B.



On Monday, April 13, 2015 at 3:35:44 PM UTC+2, Tekki wrote:
>
> Did you remember to set PERLBREW_ROOT and PERLBREW_HOME and call 
> $PERLBREW_ROOT/perl5/perlbrew/etc/bashrc before you start the application? 
> See here: http://perlbrew.pl/Perlbrew-In-Shell-Scripts.html
>
> Am Montag, 13. April 2015 13:38:59 UTC+2 schrieb Nacho B:
>>
>> THE RESULTS:
>> - If I write an absolute path por the app (*/home/tester/path-to-the-app*), 
>> Mojolicious itself complains about it cant’t found it in @INC
>>
>> - If I write *$HOME/path-to-the-app-from-the-user-directory* the script 
>> runs “fine", even it says that a .pid has been created, BUT it is not 
>> true!!!! In the log says that the app exited, and that .pid number does not 
>> exists in the running processes list in the server.
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.

Reply via email to