Vos commentaires
Fix committed
il y a 10 ans
Please give more info on what you were doing when the bug happened
I remember about that :)
It's just that I don't have enough time to fix everything immediately. The fix will arrive with the nearest build.
It's just that I don't have enough time to fix everything immediately. The fix will arrive with the nearest build.
Unfortunately multi-server administration isn't planned, just because it's too much of a work for a single person :(
However (if you're using Ajenti V) you can rsync /etc/ajenti/vh.json file, and run ajenti-ipc v reload && ajenti-ipc v apply to reload and apply the new config.
However (if you're using Ajenti V) you can rsync /etc/ajenti/vh.json file, and run ajenti-ipc v reload && ajenti-ipc v apply to reload and apply the new config.
Yes, it will be released with the nearest build.
It's a bug. Fixed.
Select www-data from the users dropdown above the cron task list, and then create your job.
You need to set up Munin to work with your server (see Munin manuals), and then use the URL, username and password that you have created.
The environment on our build server was modified by other project's activity, and resource build failed. That's the first time we shipped an update without compiled resources since alpha, if that's what you mean :)
You should be able to upgrade with yum install ajenti.
Service d'assistance aux clients par UserEcho