Ever since I upgraded to UNR 10.04, it’s taking a long time to boot my laptop, so I scoured the internet in search of a solution. Finally found one here:
http://ubuntuforums.org/showpost.php?p=9347911&postcount=10
Simple solution is to go into your BIOS and set your SATA controller to Compatibility instead of AHCI, and it boots right up!
I know this isn’t tech, but I thought it was post-worthy.
Lindsay is set to go to jail for 90 days then rehabiliation due to her avoiding her previous rehabilitation program, you can read more here:
http://www.eonline.com/uberblog/b189064_judge_sentences_lindsay_lohan_90_days.html
suPHP, made by the good people over at suPHP.org is an awesome PHP handler, both for security and for compatibility.
By default, cPanel servers will use DSO (nobody user), requiring lots of permission and ownership changes. Who wants to deal with that?
You can tell cPanel to compile in suPHP support with EasyApache, cPanels Apache and PHP configuration tool.
Sysadmins: You can see exactly how the different PHP handlers work here: http://www.cpanel.net/documentation/easyapache/ea3php_php_requests.html
Users: The gist of the document above if you’re not dizzy yet, is PHP scripts being executed with suPHP enabled, are executed under the cPanel user account that owns the site. Hence, the ‘nobody’ user no longer has any need for access, just the cPanel user.
Via SSH, as root, execute the following command:
/usr/local/cpanel/bin/rebuild_phpconf --current
[root@eclipse.lazyscripter.com] ~ # /usr/local/cpanel/bin/rebuild_phpconf --current Available handlers: suphp cgi none DEFAULT PHP: 5 PHP4 SAPI: none PHP5 SAPI: suphp SUEXEC: enabled
This means I have default PHP5, with suPHP support for PHP5. I’m good to go! If it says different, you may need to ask your hosting company about whether you should switch to suPHP or not. If you don’t see ‘suphp’ in the Available handlers line, then it means you haven’t compiled in support for suPHP into your current PHP build. You can ask your hosting company to do this for you, or myself, just shoot me an email.
If you just switched, and now you get an “Internal Server Error: 500″ message. You may want to look in cPanel > Error Logs. Most likely it’s an ownership or permission problem. By default, suPHP blocks access to files and directories with permissions of group-writeable and world-writeable, which you can change inside of File Manager or most FTP clients. Common causes for this also include bad permissions on the “public_html” folder, which, under suPHP, should have “user:nobody” ownership, permissions 0750. If the error persists, contact your hosting company, and advise them to look for SoftException in /usr/local/apache/logs/error_log which is suPHP’s way of telling you “Hey, somethings not right, or possibly insecure.”.
As always, I hope this article has been informative, hopefully I can get most of you guys to switch over to suPHP!
Ever wonder how much data is actually available on you just by visiting your Facebook page? Here’s a quick tip to find out:
Take my profile – http://facebook.com/zeadie
Now, prepend the word graph to facebook.com, like so:
http://graph.facebook.com/zeadie
You can also use your numeric Facebook User ID like:
http://graph.facebook.com/505829877
This will return all public data (or if you’re logged in and friends, then most data) in JSON encoded format like so:
{ "id": "505829877", "name": "Zach E", "first_name": "Zach", "last_name": "E", "gender": "male", "locale": "en_US" }
You can modify what is shared here: Privacy Settings
Ever wandered your way into Webhost Manager, and asked yourself what all those Exim options mean? If so, read on!
The first section is the Access Lists section, which controls blacklists and whitelists for connecting to Exim. The first 5 checks are recommended, as it will make delivering mail to your server easier. Uncheck the 6th option, “Whitelist: Trusted Mail Hosts/IP Blocks”.
Next is ACL Options, which is where most of your policy and security settings will be. I set my first two options to “0″ because I don’t have mailing lists or spammers on my server, but depending on your situation, you may want to set them accordingly. Check the next two boxes for SpamAssassin and dictionary attacks.
[X] Require incoming SMTP connections to send HELO before MAIL
This will require the sending host to send a valid HELO/EHLO (mail greeting) before any messages can be delivered. Basically, introducing yourself before you speak.
[X] Require incoming SMTP connections to send a HELO that does not match the primary hostname or a local IP address.
This will require that mail being sent to your server is prefaced with a HELO greeting that doesn’t match your server’s hostname or Primary IP address.
I usually unblock the next two options, because it has a tendency to break some mail clients.
[X] Blacklist: SPF Checking
Always enable this. This controls SPF validation. SPF is Sender Policy Framework which is a framework for verifying domain-based mail senders have authority to send mail, according to a DNS record called a TXT record. This is basically another access list, but instead of being local, it’s remote. What this does is when mail is sent, it looks up the domain the message is coming from, and attempts to find the SPF record by querying for record type TXT. The record itself contains IP groups and hostnames that are allowed to send mail as that domain. If it doesn’t validate, the mail isn’t accepted. If it does validate, it continues on to any other ACLs the message hits (ie: SpamAssassin, Rate Limiting) before it’s delivered.
Uncheck everything in the Domains and IPs section, because once you’re done with this guide, you should be pretty safe to not separate IP addresses for mail.
Accept the defaults in the Filters section. This will control what happens to spam, and the filters there are correct by default.
Under the Mail section, check the following:
Uncheck everything else under Mail.
In the next section, RBLs, check both boxes to enable both Spamcop and Spamhaus Blacklist Checkers, you can even add your own by clicking [Manage].
In the SpamAssassinTM Options section, check the top box to enable SpamAssassin globally without the option for users to disable it, and set the field below it to 1/16th of your RAM in MB. Example: 4096/16 = 256
Then, click Save at the bottom, and Exim should restart itself, and you’re done in WHM.
Then, for each of your cPanel accounts, go into Mail -> Default Address, and select Discard, and put a custom message beside it. Try to be as nondescriptive as possible, something like:
Mailbox for this account is currently unavailable
Make sure to limit the amount of Autoresponders you have. By design, they respond to every message sent to it, regardless of whether it exists or not. This is an easy way to get blacklisted.
Also, try to avoid the usage of Boxtrapper, as it does almost the same thing, except it only sends return messages until the recipient is verified by either the user or by Boxtrapper.
That’s all for today folks! Happy emailing!
Alright guys, this has been a long time coming, so I have created a complete setup guide for Google Analytics.
Google Analytics setup involves using a small chunk of ssl-aware javascript code to use your client’s browsers to gather information about:
* What site they are coming from to get to yours
* What search terms they entered to find your site
* Client stats breakdown by OS, Browser, Geolocation, and much more
Click on the direct link above to get started. Once you’re verified, sign into http://www.google.com/analytics/
Then, click on Add Website Profile to add your website.
Then, fill out the URL of your site, example http://lazyscripter.com and click Finish.
You’ll get a screen like this:
Save your UA String at the top, you’ll need it for the next part.
Now, goto your WordPress Admin Dashboard, usually http://www.yourwebsite.com/wp-admin, and sign in as the administrative user.
Next, we’re going to install a plugin called Google Analytics for WordPress which you can do from the Plugins > Add New menu as shown below.
After you click Install Now, it will setup the plugin. On the next screen, click Activate Plugin.
Then, go to Settings > Google Analytics and you should make the options look like so (don’t forget to put in your UA String).
Once you click the checkbox next to Show Advanced Settings, another menu group will open up, it will look like this.
At this point, go ahead and customize your settings the way you see fit. When you’re finished, click Update Google Analytics Settings. You’re done!
Now, just sit back, keep posting, and visit Google Analytics to see your site’s traffic and visitor stats!
