You can use the linked page here and follow their instructions (close to 1:1 match, but the differences are pretty obvious) to disable minidlna.
I wouldn't bother disabling scan and the webpage as the benefits are very limited towards performances of the drive and fiddling with configuration and script files becomes less obvious.
By simply disabling minidlna you save:
1) memory;
2) CPU;
3) battery (as a direct consequence of bullet 2, being minidlna a resource hog - about 45% continuous CPU usage on my GFS).
Disabling scan saves you about 20% CPU for a limited time (a few minutes at startup) but then the process disappears having completed its task (unless it's the first scan or you added ALOT of contents since previous scan!).
Disabling the webpage saves live memory usage but pretty much no CPU (unless you use it for some reason, but then you'd miss the point of using SAMBA), but prevents you from using some other useful features like joining existing WLANs or changing security (that are available through other scripts, but harder to manage IMHO).
Anyway, preventing minidlna from running is a very good thing overall, (if you don't strictly need it) for the list of reasons above and allows for an easier streaming of content; i was not able to stream full HD contents before, but when I commented out minidlna from the startup and resume scripts I gained ability to stream those as well and the CPU of my GFS remains constantly UNDER 20%...
