No.
Seems to be that tracking Data Transfer other than by IP address (which is the easiest way to do it), requires add-on scripts and/or modules.
Seems to be that tracking Data Transfer other than by IP address (which is the easiest way to do it), requires add-on scripts and/or modules.
Such as: NetSaint, Big Brother, Big Sister, or programs along those lines. Your favourite Search Engine can give you more information on them as I don't have their URL's handy.
It does track the bandwidth.... it just tracks it on hosting_company.com rather than the correct domain. The reason for this is because apache is logging the bytes to the domains bytes log which in this case would be hosting_company.com rather than the actual users domain name.
Hello
This means that users can call files via http://ip/~username
and bypass the bandwidth limits.
It is a serious problem as people seem to have found out about it.
We had 4 users rip over 400Gb this month before they were caught.
Its something that really needs looked at as shared SSL traffic is also not counted.
I copy access_log to a web viewable folder and do manual trawls.
I then suspend the user and ask them to stop doing it.
Over 20+ servers this is a very big job and something which could be automated in WHM.
It should be possible to parse the access_log and look for ~username and add the bytes to their total.
Another option is to disable access via ip/~username
bu this means people cant upload prior to their domain resolving which is not possible for comercial reasons.
Another way would be to park a subdomain on top like username.servername.com with the other method disabled
However this would prevent shared SSL except with a wildcard and such an arrangement is not automated in WHM so it would be a lot of work when setting up accounts.
Nick either has to look at adding the bandwidth from access_log to the users total or change account set up so it parks a subdomain instead of using ~username
Either way something does need done as the present status is not satisfactory.
I would advise anyone reading this to check access_log for any high bandwifth activity by username.
You may be in for a shock.
Gordon
This means that users can call files via http://ip/~username
and bypass the bandwidth limits.
It is a serious problem as people seem to have found out about it.
We had 4 users rip over 400Gb this month before they were caught.
Its something that really needs looked at as shared SSL traffic is also not counted.
I copy access_log to a web viewable folder and do manual trawls.
I then suspend the user and ask them to stop doing it.
Over 20+ servers this is a very big job and something which could be automated in WHM.
It should be possible to parse the access_log and look for ~username and add the bytes to their total.
Another option is to disable access via ip/~username
bu this means people cant upload prior to their domain resolving which is not possible for comercial reasons.
Another way would be to park a subdomain on top like username.servername.com with the other method disabled
However this would prevent shared SSL except with a wildcard and such an arrangement is not automated in WHM so it would be a lot of work when setting up accounts.
Nick either has to look at adding the bandwidth from access_log to the users total or change account set up so it parks a subdomain instead of using ~username
Either way something does need done as the present status is not satisfactory.
I would advise anyone reading this to check access_log for any high bandwifth activity by username.
You may be in for a shock.
Gordon
We offer personal home pages with our dialup service. One of our admins made a c program which parses each &~username& and calculates the bandwidth usage from the access_log file.
Something like this can be modified to parse the cpanel logs and add it to the byte count file of the domain that matches the username.
This would definatly solve the problem. He made the program within an hour at the time, it shouldn't be difficult for Nick to impliment something like that in cpanel for the share ssl and main server log files. It is much needed..
** An IMPORTANT FEATURE NEEDED and has been discussed many times in this forum **
Something like this can be modified to parse the cpanel logs and add it to the byte count file of the domain that matches the username.
This would definatly solve the problem. He made the program within an hour at the time, it shouldn't be difficult for Nick to impliment something like that in cpanel for the share ssl and main server log files. It is much needed..
** An IMPORTANT FEATURE NEEDED and has been discussed many times in this forum **