10.11.2, a bleeding edge current version of OS X. Here's the video:Huh, I can't reproduce it. Which exact OS X version do you use?
Could you please tell me why do you need a daemon process? We were thinking about implementing it when we were starting OS X version development, but in the end we've chosen the current way just because we had not found enough pros for daemon.
My use case may be slightly different from regular, I have over 30 devices accessing the internet, but live in the middle of the woods and my only connection is a LTE link with 100 GB transfer cap. I therefore use an array of means to cut the usage, including a heavily tuned caching proxy, extensive blacklists on host file level on my router and ad blocking.
A daemon process would allow me to streamline the workflow - I do not ever need to log on to my Mini server (pictured above) which runs my servers (SQL, Mail, Web, Media, Squid caching proxy etc). In case of a catastrophic failure it would just restart and continue to work as intended, the daemons would just start providing the services. And I never do log on to a server directly. It's on the login screen permanently, does not have a monitor attached to it, I actually had to install something that would fool the system into thinking there is a monitor connected in order to record the video.
A software that starts running after logging on does not have these qualities, obviously. Yes, I could log in manually (or use automatic login) to the server and then lock the screen, but this is at least cumbersome (not to mention I would NOT allow my server that holds 19 years worth of my email to autostart and auto log in).