If Outlook 2007 is constantly asking to enter your password, even though you've enabled Remember password, try the following:
The Synology website has a problem for some time now. When surfing to the main website (http://www.synology.com/), you get the following error:
This is not really good publicity if you ask me.
For those that require information on the website, can either google for it, or use the direct link: http://www.synology.com/enu/index.php.
One of the highlights would be a better compliance with industry standards (HTML5, CSS3, etc.). Does this mean that the horrid problem of browser incompatibility (especially between IE and all other browsers) will finally be resolved? I sure hope so...
It is not possible to convert disk files from thick to thin, in-place. Instead, cloning the disk (or machine) allows you to change the provisioning type and thus enabling to have a thin disk. After the clone is complete, delete the original and you're good to go.
You can either clone a complete machine, or just clone a disk using the CLI or service console:
vmkfstools -i <srcDisk.vmdk> -d thin <dstDisk.vmdk>
Be careful of installing Google Chrome on a Windows XP computer with an Intel 915i graphics card on board. I ran into an odd problem at a client, who had recently installed it. Occassionally, the system would bail out with a BSOD, and a vague error code. At first, I suspected a hardware problem, but letting WinDbg loose on the minidump file revealed the true culprit.
Apparently, there's a conflict between the graphics driver of the Intel 915 and Chrome, causing the BSOD. A detailed analysis in WinDbg revealed the causing program as chrome.exe. See the attached text file for a full log of the problem.
The client stopped using Chrome, and his odd BSODs went away.
Funny guys over at Belgacom. Their B-Box status page shows this as line status for a VDSL connection:
This package provides files to enable syntax highlighting in nano when editing shorewall configuration files, making it easier to maintain these kinds of files.
For a shell script to determine its own location, you can use this code snippet. It takes relative and absolute paths into account.
#!/bin/bash if [[ $0 == '/'* ]]; then MYLOCATION="`dirname $0`" else MYLOCATION="`pwd`"/"`dirname $0`" fi echo "My location is: $MYLOCATION"
If for some reason you lost your SSH server keys, sshd will fail to start with error:
Could not load host key: /etc/ssh/ssh_host_rsa_key Could not load host key: /etc/ssh/ssh_host_dsa_key
You can recreate your host keys with these commands:
ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key
After recreating the keys, you will probably have to let your clients know as with the change of keys, they'll probably get warnings about it (Linux SSH will not even connect until you kick out the old keys).