FUTURE REQUEST - Stats control per domain / client

[moja]

Is it possible to add possibility to add one option - have stats disabled/enabled by default for all users and second feature - enable/disable stats generation only for specific client?

Because of ...

We installed DirectAdmin server and integrated AWStats.

Now AWStats are enable and doing statistics for all clients and domains. Is there a possibility to have AWStats disabled for all domains and be able to enable generation of statistics only for clients who will request that at our admin?

Because from our experiences - 99,9 % of our clients who are looking for webhosting will take a hosting with statistics - but they will never use them, because they are using Google Analytics or other similiar services which are better for them and provide little bit other kind of statistics. We think it is wasting of server CPU to process stats for everyone every day in this situation and we would prefere to disable stats for all clients by default - and enable awstats only for clients who will request that at out tech. support.

Is this possible with DirectAdmin?

Thank you.

 

[hansmiddelhoek]

For e-mailonly customers AWstats is useless and only takes up drivespace. IMO it should be possible to disable AWstats for certain accounts for several reasons.
Nice feature.

 

[moja]

Any others? Any news regarding this issue? Thank you.

 

[moja]

I got info from John (see bellow), does anyone know how to setup that list of users to allow to have awstats run? Any idea? Thank you very much.

---

As for the DirectAdmin version, you can control it per user, but only if you edit
/usr/local/directadmin/scripts/awstats_process.sh

and setup a list of users to allow to have it run..
and for any user not allowed, just do "exit 0;" before it runs to abort.

Thank you,

John

 

[BATeller]

great feature idea. Please!

 

[ranz]

+1 for me.

 

[interfasys]

I got info from John (see bellow), does anyone know how to setup that list of users to allow to have awstats run? Any idea? Thank you very much.

The script is called with 2 arguments, the user and the domain.
If you manage things at the user level, then put a list of users in a file, otherwise use a list of domains.
Then you just check the user or domain against elements of the list and only run the script for the ones you want.

 

[hansmiddelhoek]

I don't see /usr/local/directadmin/scripts/awstats_process.sh as a nice solution for this. Maybe that's usable if you only have 10-20 accounts on a server, but with a few hundred it's unmanageable that way.
IMO it should be a feature within the control panel itself. With a script it will soon get a mess, if you remove an account from the server, you also should remove the user from that script. Not a real solution for this feature request.

 

[interfasys]

I never said that you need to add people to the script, you add them to an external file or grep their preference file to find out whether it's activated or not.

 

[hansmiddelhoek]

I never said that you need to add people to the script, you add them to an external file or grep their preference file to find out whether it's activated or not.

That's true, but somewhere you need to specify which account may use awstats. You said to grep the preference file to find ot if it's activated, but that's the problem, there's no preference file where you can specify this. That's why the topic starter asked for this feature. As DirectAdmin support e-mailed to moja:
------------------------------------
As for the DirectAdmin version, you can control it per user, but only if you edit
/usr/local/directadmin/scripts/awstats_process.sh

and setup a list of users to allow to have it run..
and for any user not allowed, just do "exit 0;" before it runs to abort.
------------------------------------

Somewhere you need to add and remove users to a list and that should be done manually as far as I can tell.

 

[interfasys]

Just add a custom feature to your user's package and then grep it in their preferences.
I'm just offering ways to do it now, but I agree that awstats should have been included in the user's preference file since the the introduction of that feature.

 

[floyd]

There is no "I don't care" selection in the poll. I know people think that if you don't care then you shouldn't vote. But I do think its useful to know who actively does not care.

What if 7 say yes and 1 says no. It makes it sound like we should do it.

But what if 50 actively say we don't really care. Well then DA knows that most people don't care and they should not bother with it for now.

That is just my opinion for whatever that is worth.

 

[chao]

moja,

Could I just ask you which version of the awstats plug in you have implemented?

I have installed the stats control version, but am having difficulty getting it to work properly.

Thanks

 

[nicsopon]

I got info from John (see bellow), does anyone know how to setup that list of users to allow to have awstats run? Any idea? Thank you very much.

---

As for the DirectAdmin version, you can control it per user, but only if you edit
/usr/local/directadmin/scripts/awstats_process.sh

and setup a list of users to allow to have it run..
and for any user not allowed, just do "exit 0;" before it runs to abort.

Thank you,

John

The script is called with 2 arguments, the user and the domain.
If you manage things at the user level, then put a list of users in a file, otherwise use a list of domains.
Then you just check the user or domain against elements of the list and only run the script for the ones you want.

I'm a new linux user. Could you give an example of the full modificaion for us to follow.

Thanks & Best Regards