PHP Warnings on Daemon Run (opendir)

[apinto]

Hello,
On my development machine when I run the daemon it takes a HUGE amount of time (around 5min for each daemon run... and returns tons of tons of PHP Warning like this:

PHP Code:

PHP Warning:  opendir('/var/sentora/hostdata/my_account/public_html/my_domain_dev/web/app/themes/my_folder/node_modules/asset-builder/node_modules/main-bower-files/node_modules/vinyl-fs/node_modules/glob-stream/node_modules/unique-stream/node_modules/es6-set/node_modules/es5-ext/test/string/raw'): failed to open dir: Operation not permitted in '/etc/sentora/panel/dryden/fs/director.class.php' on line 347 


Any idea what i may be?

the node_modules has a ton of files... that might explain it...

[Me.B]

Why do you have so long opendir?

opendir('/var/sentora/hostdata/my_account/public_html/my_domain_dev/web/app/themes/my_folder/node_modules/asset-builder/node_modules/main-bower-files/node_modules/vinyl-fs/node_modules/glob-stream/node_modules/unique-stream/node_modules/es6-set/node_modules/es5-ext/test/string/raw'):

usually opendir are only 6 levels never beyond, as you can't set them so long?

We are talking here about sentora daemon or user daemon?

[apinto]

Hi Me.B Thank you for your reply!!

I'm talking about running:

Code:

php -q /etc/sentora/panel/bin/daemon.php

On the command line.

UPDATE/EDIT: This happens when calculating disk usage.

I understand the issue might be related to the huge file path (seriously it's really huge, I admit).
However that "huge" path is a necessary evil of my workflow (and honestly of any modern package management workflow like npm, composer, bower, etc; as they import other packages).

Is there any way of getting around this?
Specially without hacking too much

[Me.B]

I think we have a tweak for BW already that 5050 made and would later opt for disabling BW/ disk usage by admin for some users.

Currently I don't see a solution.

M B

[apinto]

My concern is infact the performance of such file setups.
Because the final disk usage is correctly read.

[apinto]

Thank you for reply Me.B!
I'll look into a different way to get around this.

[Me.B]

My concern is infact the performance of such file setups.
Because the final disk usage is correctly read.

You can still lower cron priority so it uses less CPU by the way ( We do it already).