Suggestion: Neighborhood Watch

With the onslaught of recent uptime/downtime and performance issues, I’d like to see who else would be interested in having a list of other users on a particular server. There is not one person that has had performance issues that hasn’t wondered if its an inconsiderate neighbor hogging resources. This would give us the chance to monitor our neighbors and report issues which we think might affect our own services. Furthermore, it would encourage users to be more cautious with the resources they are using in consideration of others.

There’s already a group of people that do that.

They call themselves Dreamhost.

I heard they even get paid to do it.

:stuck_out_tongue: Save up to $96 at Dreamhost with ALMOST97 promo code (I get $1).
Or save $97 with THEFULL97.

How clever you are.

It would still benefit some of us that tend to have these issues on a regular basis to find out if the issue IS related to our neighbors and WHY.

You can’t monitor other users on your server. And I don’t want the other hundred or so users on my server asking me 10 times a day if I’m also having trouble with my sites. If they really think there’s a problem, that’s what Support is for, or these forums.

Not to mention that an experienced user can diagnose a lot using command line (and other) tools from their account and from home. If it’s an inexperienced user, this (forum) is the place to ask for help in diagnosing a problem.


There’s already a process to handle that. When server performance is lacking, let them know and they’ll figure out why.

If Dreamhost wasn’t already doing it, you’d never see people here whining about being spanked for hogging resources.

:stuck_out_tongue: Save up to $96 at Dreamhost with ALMOST97 promo code (I get $1).
Or save $97 with THEFULL97.

There are potentially at lot of issues involved with that, some of which have already been discussed in other posts.

If you are really that interested, get familiar with the shell…and explore a bit (cd …; ls -la; users - etc.). :wink:


points out privacy issues

I’m fine with the current system of reporting outages anyways. I don’t host any “business” sites here though, where I’m making $1,000/hit (like some people randomly claim), so if I have to wait an hour or two for it to be fixed, it doesn’t bother me :slight_smile:

Chips N Cheese - Custom PHP installs and the like!

Not a good idea.

You wouldn’t believe how many people use plaintext passwords in command invocations (wget http://username:password@somesupersecretsite ? lftp ? mysql -u admin -p yeahthisissecret ?). Sure it’s their own fault, but a simple ps faxuwww or top (or even an automated script doing that) can easily net you lots of passwords from “your neighbours”.

My server didn’t have grsec enabled for a while. It was indeed nice to see some of the royal a**holes driving the load up to 20 or more (yes buddy, it’s a splendid idea to run 20 high I/O and high CPU processes at once) and get some insight into what services run on a single server, but the potential for abuse is definitely there.

You can of course see home directories. Some people even get their permissions wrong and you can descend into their homes. (it might be a good idea to set the permissions of /home from rwxrwsr-x to rwxrws–x to reduce the amount of information you can glean from there, though I suppose /etc/passwd is even more of an information-well).

And for yourself, if you do not run any websites on a particular account, there is absolutely no reason to have permissons of 755 or 751 on your homedirectory. 750 is perfectly fine (if you want other accounts within your group to have access), or even 700. Even if you do run a website, all that is STRICTLY needed is 001, though most people would do well with 701 instead (never remove your own access unless you absolutely know what you are doing).

And one last thing; Privacy is important. There is no reason you should be able to “monitor” exactly what I do. Maybe what I do violates some code of ethics you have (there are pr0n-sites on DH, after all) and you’ll come up with some excuse to bash my account to support. The less you know about my account and I know about yours, the better – not only for me, but for you as well. If your account gets compromised, at least the attacker can’t see what fastcgi apps I am running, what paths I am using, and other “interesting” things that might make it easier for them to compromise my account, as well (it’s infinitely easier to compromise more stuff once you have a foothold on a server, i.e. once one account has been exposed; and really, do YOU trust all the silly passwords people set for their accounts ?)