Quote:
Originally Posted by jubal
The AUP entry you reference does not spell this out -- specifically, preauthorized or implicit access to a customer's VPS for "monitoring". Is this VPSLink's official interpretation of "monitoring" ?
I read the AUP before purchasing the service. I assumed at the time that monitoring meant "external monitoring", and did not include implicit permission for internal access.
|
To clarify, we do not actively monitor the contents of individual virtual environments' file systems - in the event that a DMCA take-down notice is received or an abuse report is submitted, our technicians will follow up with an inspection of the virtual environment purported to be the source of the copyright violation or malicious activity.
Additionally, if your VPS is determined to be using resources in excess of its allocation to the detriment of other subscribers, (i.e. in the case of a runaway process consuming an inordinate amount of CPU time) our system administrators may investigate the processes running on your VPS to identify the source of the problem.
Quote:
Originally Posted by jubal
I was fine with this up until the point where "all possible causes" now seems to include logging into my system. I purchased a service that is advertised as unmanaged, and I would like it to remain that way.
Please do not permit those exceptions to happen again for my case. Also, please consider updating the AUP to spell out the distinction between external and internal modes of monitoring.
|
By all appearances, you should not have a need to contact our support staff regularly for assistance so I would recommend that you include a note that you would prefer our technicians refrain from accessing your VPS should the need to contact our staff for support arise.