Other folders created in website dir

[spikes]

Hi,

Yesterday I created 2 new cron jobs. I did not have cron jobs before. Today I login with ftp of the website and I see new folders together with default folders.

bin cgi-bin dev etc home lib log ssl tmp usr var web

Is this normal? How did the folders get there? Thank you

I see this in the cron log

Warning: Perl versions before 5.6 cannot handle nested includes
Warning: Perl versions before 5.6 cannot handle nested includes
Warning: Perl versions before 5.6 cannot handle nested includes
Warning: Perl versions before 5.6 cannot handle nested includes
Warning: Perl versions before 5.6 cannot handle nested includes
Warning: Perl versions before 5.6 cannot handle nested includes
Warning: Perl versions before 5.6 cannot handle nested includes
mkdir: cannot create directory `/var/www/clients/client0/web2/var': File exists
mkdir: cannot create directory `/var/www/clients/client0/web2/var/run': File exists
ERROR: /usr/bin/lesspipe does not exist

usermod: unlocking the user would result in a passwordless account.
You should set a password with usermod -p to unlock this user account.
ERROR: /usr/bin/lesspipe does not exist

usermod: no changes
ERROR: /usr/bin/lesspipe does not exist

usermod: no changes
Warning: Perl versions before 5.6 cannot handle nested includes

[pititis]

Yes it's normal. When you select "chrooted cron" for a customer these folders are created. Cron will run under a jailed environment to limit the user access and commands, they can only run command from this environment.

Cheers

[spikes]

Originally Posted by pititis

Yes it's normal. When you select "chrooted cron" for a customer these folders are created. Cron will run under a jailed environment to limit the user access and commands, they can only run command from this environment.

Cheers

I do not have any customers (clients) so when you say "chrooted cron" exactly what does this mean? I have added the cron job like this

http://mysite.com/cron/task.php

Is there a difference in methods when I add it like this

/usr/bin/php /var/www/clients/client0/web2/web/cron/task.php

Is it dangerous to have these files there?

[pititis]

I do not have any customers

client0 is your client.

Check client limits under Client->yourclient->limits->Max type of cron jobs (login as admin...)

[gapa]

This happens to me to. And no matter what I select for "Max. Allowed Cronjob types (chrooted and full implies url)". I can see that all those additional folders get created when I add shell user. Not before. How can I disable creating all those folders? When I was at another provider and had reseller account I didn't had those problems. It was version 3.0.3.3 and now I have 3.0.4.
Any ideas how to disable creating all those folders?

[gapa]

I think I got it. If I give to user also "SSH-Chroot Options" = None and that user creates shell user with option "Chroot Shell" = None then only default folders are created. But in that case shell user is free to go anywhere on the system. Won't be able to run any commands though. And if user has only Jailkit option for chroot option, then additional folders are created. And is of course jailed in his own environment.