Samstag, Februar 14, 2015

miniDLNA doesn't seem to update database autonomously

miniDLNA works perfectly for me and lets me access all my media on Android devices, XBMC, internet radio, and a sony bluray player as well (as long as the device has the right decoders).
But, for some reason, it doesn't seem to add new files which I add to its folders.
Now if found this post

In summary, the most reliable way to have MiniDLNA rescan all media files is by issuing the following set of commands:
$ sudo minidlna -R
$ sudo service minidlna restart
However, every so often MiniDLNA will be running on a server. Here is a client-side script to request a rescan on such a server:
ssh -t server.on.lan 'sudo minidlna -R && sudo service minidlna restart'
AzP already provided most of the information, but some of it is incorrect.
First of all, there is no such option inotify_interval. The only option that exists is notify_interval and has nothing to do with inotify.
So to clarify, notify_interval controls how frequently the (mini)dlna server announces itself in the network. The default value of 895 means it will announce itself about once every 15 minutes, meaning clients will need at most 15 minutes to find the server. I personally use 1-5 minutes depending on client volatility in the network.
In terms of getting minidlna to find files that have been added, there are two options:
  • The first is equivalent to removing the file files.db and consists in restarting minidlna while passing the -R argument, which forces a full rescan.
  • The second is to rely on inotify events by setting inotify=yes and restarting minidlna. If inotify is set to =no, the only option to update the file database is the forced full rescan.
Additionally, in order to have inotify working, the file-system must support inotify events, which is not the case in most remote file-systems. If you have minidlna running over NFS it will not see any inotify events because these are generated on the server side and not on the client.
Finally, even if inotify is working and is supported by the file-system, the user under which minidlna is running must be able to read the file, otherwise it will not be able to retrieve necessary metadata. In this case, the logfile (usually /var/log/minidlna.log) should contain useful information.


Mittwoch, Oktober 30, 2013

samba without authorization


$sudo vi /etc/samba/smb.conf
and set interfaces to lo and your local network interface. In my case: eth1.
interfaces = lo eth1
bind interfaces only = true
Now, it is time to smoothen samba default security by changing the security variable: security and make sure it is set to share instead of user and that guest account is enabled:
security = share
guest account = nobody
Now, we can create a share to be accessible to guest users:
[Guest Share]
        comment = Guest access share
        path = /path/to/dir/to/share
        browseable = yes
        read only = yes
        guest ok = yes
You can now test that your configuration is good using testparm:
$ testparm
If everything is fine, it is time to reload samba service to have your new configuration taken into account:
$sudo /etc/init.d/samba reload

Mittwoch, Oktober 23, 2013

Systembackup using dpkg and dselect

Systembackup by integr8e
As a result of many reinstallations, I've begun developing a method that quickly allows me to restore my new installation to the setup of my old one. As such, I decided to share my knowledge:


- To create an easily restoreable list of all installed software on your system (from the repos), open Konsole and enter the following command:

dpkg --get-selections | grep [^de]install$ > installed-software.txt

- That will create an entry in your "/home//" directory entitled "installed-software.txt" ( is your username).

-> [u]BACKUP

- Backup all your important files to an external storage device (hard drive / flash disk); you may wish to backup your "/etc/X11/xorg.conf" and "/etc/apt/sources.list" configs. If you have the Medibuntu/Wine repo(s), you'll need to additionally backup your "/etc/apt/sources.list.d" directory. For an excellent guide on backing up using the "dd" command, see Qqmike's [u]dd Command (

- I generally format my external hard drive as XFS ( because it allows me to quickly transfer/move large files. You can format your hard drive using any number of formatting utilities; I prefer using the GParted LiveCD (

- It's a very good idea to backup periodically, because you'll be out of luck if you don't have a copy and you frag your system beyond repair. Also, keep a list of any software you installed outside of the repositories (such as those downloaded/installed from 3rd party websites).


- Configure your BIOS to boot from CD first. Then, insert the Kubuntu installation CD (I used the Alternate CD for this example, but it doesn't matter which you use), and reboot. When the CD loads, choose the "Install a Command-Line System" option, fill out all the requested information, and choose the "Manual" option to partition your hard drive.

- I would suggest creating 3 basic partitions: SWAP, "/" , and "/home". For SWAP, create a partition roughly 1.5 - 2 times the amount of RAM you have installed (SWAP is similar to "Virtual Memory" in Windows). Then, create your "/" (or "/root") partition. You shouldn't need more than 8 GB for your "/root" partition; if you ever use more than 10 GB, my hat's off to you :o You can make it any format you wish (check the list of File Systems ( (FS) to see which you prefer; just look for the “Linux” entries in the far-right column). Finally, create a "/home" partition; choose whichever FS type you would like to use, and create it as large as you want (this is the partition you'll be storing your personal data in). If you already have a separate “/home” partition, keep it the way it is (don't format it), and select it again as your “/home” partition. This way you can keep your application settings/customizations and personal data intact. Then, use the same username you had before so the installer will associate your previous “/home//” directory with your new “/home//” directory.

- I create an additional 200MB “/boot” partition for the GRUB bootloader, and format as [u]ext3 (; I do this because my FS of choice is XFS, which currently is incompatible with GRUB. I also create an extended partition where I create logical “/root” partitions; this way, I can install as many operating systems I want, and use the same “/home” directory (BIOS currently only allows 4 primary partitions on your hard drive, including 1 extended partition; an extended partition is a primary partition within which you can create as many "logical" partitions you want).


Once Kubuntu is installed, remove the installation CD from your computer and reboot. Login, restore your repositories, and update your system with the command

sudo aptitude update; sudo aptitude safe-upgrade

- You're now ready to restore all your previously installed software. To do so, you'll need the dselect package manager:

sudo aptitude install dselect

- Restore the “installed-software.txt” file you created, and reinstall your software with the following commands:

sudo dpkg --set-selections < installed-software.txt

sudo dselect

- Choose option "3. [ I ]nststall Install and upgrade wanted packages." That should install everything you had before!

- You'll have to manually install anything you installed outside the repos, sorry :P

- Most of your application settings will already be in your “/home/[username]/” directory, for those that aren't (such as your “xorg.conf”), simply replace the existing ones with those you backed up. Once everything has reinstalled, start KDM with

sudo /etc/init.d/kdm start

Everything should now be as it was before ;)

;D ;D ;D

Edit: Using the many suggestions of those who contributed to this thread, I've re-written it in attempt to make it simpler, easier, quicker, and more effective. Thank you all who helped :)

Sonntag, Oktober 06, 2013

"Trash has reached maximum size"

"Trash has reached maximum size"
This message came up since a long time on my linux desktop when I tried to use the trash bin icon to delete stuff. Emptying the bin didn't help and didn't make sense, because there's still a lot of space available on my hardrive.

I found the (simple) solution finally here:


The solution to my problem is the following:
Code: Select all
root@sega:/home/ilj % mv /home/ilj/.local/share/Trash ~/
The error message is bogus, though. The Trash folder did not contain any files:

and there was a one string entry only in the metadata file. Moving Trash folder allowed me to start using it as expected instantly.

Freitag, Mai 17, 2013

USB Laufwerksbuchstaben fest zuordnen unter Windows XP

Control Panel
-> Verwaltung
-> Computerverwaltung
-> Daträgerverwaltung

Montag, März 25, 2013

compiz 12.04 rotating cubes flash

solved in 12.10.

most fixes in 12.04 available by

sudo apt-add-repository ppa:vanvugt/compiz-preproposed
sudo apt-get update
sudo apt-get install compiz=1: compiz-core=1: compiz-gnome=1: compiz-plugins=1: compiz-plugins=1: compiz-plugins-default=1: libdecoration0=1:

hold compiz with:

{ echo compiz hold ; echo compiz-core hold ; echo compiz-plugins hold ; echo compiz-gnome hold ; echo compiz-plugins-default hold ; echo libdecoration0 hold ; } | sudo dpkg --set-selections

Montag, Februar 25, 2013

Keep console application open in MS Visual C++ 2010 Express

Usually the console window closes immediately after execution.

To keep it open, one could change the program and add e.g. a cin.get().

But there is a way to keep it open without changing any line:

Bitte Rechtsklick den Projektnamen, und gehen Sie auf der Seite Eigenschaften bitte erweitern Sie Konfigurationseigenschaften-> Linker-> System, wählen Sie bitte die Konsole (/ SUBSYSTEM: CONSOLE) im Dropdown-SubSystem. Da, in der Standardeinstellung das leere Projekt nicht angegeben ist.

in english:

Please right click your project name and go to Properties page, please expand Configuration Properties -> Linker -> System, please select Console (/SUBSYSTEM:CONSOLE) in SubSystem dropdown. Because, by default, the Empty project does not specify it.