After configuring Samba, the daemon takes forever to start. Once this was solved, on big file transfers smbd caused massive load and ate up all the CPU.
[Solutions]
As Devil is a CD Distro and not installed to the HDD, make sure you configured all the pathes for logfiles etc. to locations where samba really can write to. Double check if the write permissions are sufficient! If samba has trouble writing its logs, it will still start up - but every operation it usually would access the logfile for is incredibly slow. Looks like a timeout
The problem with the CPU hogging and shit performance on big file transfers is not yet fully solved, but partially: Appearently on our Shuttle G20S5 (XPC) Devil Linux hat problems with the on-board IDE Chipset. Same samba configuration on other HDD's (USB externals) showed very good performance. We are investigating this problem further.