Note that i only mention the differences between them.

Spotify

Good:

1. It`s fast to start!
2. Streaming starts fast!
3. You can create lists that will work when offline
4. Does not have any journalists to pick out nice songs and kinda create a community around that
5. It`s free – So you can test it better before paying for it

Bad:

1. They are starting to loose music due to bad payments to producers etc
2. Not too much Norwegian music (for those who care )

Wimp

Good:

1. You can see others play list easier than in Spotify (at least the most popular)
2. The design is more white-ish than Spotify
3. Easy to see the play queue and what have been played
4. Easier access to songs/albums within a genre

Bad:

1. No free version, although you get the first 30 days free
2. No offline ability, d`oh!
3. I cannot set my own password, why?
4. Its only in Norwegian for now, and it requires a Norwegian cellphone(?)
5. When i forget the generated password, i get the same password sent to me..so long for security
6. It uses a lot more resources (10 times the RAM of Spotify…)
7. Due to #6, it is very slow on some machines
8. The “change password” link in the program sends me to a page without ability to change password
9. On one of my computers, i cannot restore the program when sending it to the tray bar..whoops

In conclution

I will keep to Spotify for as long as they have enough music, or until Wimp fixes some of the most annoying things.

Looking for more tests?

A norwegian test in vg.no
A norwegian test in nettavisen.no
A norwegian test with focus on sound

1) Installing php5-devel (PHP development libraries)
2) Installing the pecl package ssh2
3) Restarting Apache

And voila, the SSH2 option appeared!

For this you have 2 possible solutions:

1) Patch munin-graph manually using:
http://munin-monitoring.org/svn/munin/branches/debian/lenny/trunk/debian/patches/380-munin-graph-utf8.patch

Note that the line numbers are a bit off if you are using another version.

2) Find the munin-node plugin that causes the problem(aka having some none utf-8 characters). Most likely it is the following line in the plugin hddtemp_smartctl:

print “graph_vlabel temp in °C\n”;

Change it to:

print “graph_vlabel temp in C\n”;

Restart the munin-node and you should not get more trouble, at least from that plugin.

Locate the lock_file setting:

lock_file=/var/run

And change it to another path, like for example /tmp.

Start up Nagios again and it should be much happier

USE DATABASE mysql;
SET PASSWORD FOR root@localhost=PASSWORD(‘yournewpassword’);
FLUSH PRIVILEGES;

And voila! You have changed your password.

PS: If you have a “problem” with beeing able to login to MySQL without using password (even when it is set in MySQL), try to edit or delete ~/my.cnf, since that holds information used to avoid the login promt.

1) Installed a 32bit virtual Ubuntu machine, and converted the Groupwise installer to a .deb package with “alien -c filename”.

2) Moved the .deb package back to the host machine.

3) Installed 32bit java libraries “sudo apt-get install ia32-sun-java6-bin”

4) Forced installation of the Groupwise client “sudo dpkg -i –force-architecture novell-groupwise-gwclient_8.0.0-84911_i386.deb”

5) And it works

java.lang.IllegalArgumentException: Object: Ting@193c227 is not a known entity type.

This will occur when you have redeployed an app f.ex through Eclipse to Glassfish, the Glassfish server has not quite understood that it`s time to update its version, so what you need to do then is to simply restart the server (or domain).

The solution is pretty simple, run this query in the database:

“ALTER TABLE sessions CHANGE a_session a_session LONGBLOB;”

Then clear the table with:

TRUNCATE TABLE `sessions`;

Any logged in users will be logged out, but the problem should disappear.

If the problem is that the asadmin start-agent command simply times out/uses a long time to start, and even possibly returning a filenotfoundexception. The problem could be as simple as a firewall blocking traffic to/from the master-node. A quick way to check it is to simply disable the FW.

Note that if the master-node does not see the node-agent status, it is also caused by FW-issues, fix the FW and then restart the node-agent(s), then it all should work like a charm!

Add this to ~/.vimrc:
set backspace=indent,eol,start