I am using "edison-image-rel1-maint-rel1-ww42-14" from the downloads page, I believe this is 14, where can I find 16.
If the mDNS.service is not needed, you could disable it through: systemctl disable mdns -- until it gets resolved.
My mDNS is not as chatty, though I have had issues with configure_edison.service being quite chatty in the same manner
Thanks for the info, I learned already about the disable service option. I like to keep mDNS because it is very handy to communicate with the device e.g. ssh email@example.com This works independent of the network environment (in my case at home or at work).
BTW: I know Bonjour very well because we got a own implementation in our solutions. I like to raise the Edison mdnsd issue because it will hurt in many cases when users get out of space in the root file system. My current workaround is the log limitation SystemMaxUse=20M in /etc/systemd/journald.conf
Just for my own understanding,
Is the mDNS service being chatty while you are using it directly, or when it is available but not in use, or both?
If you could also try it enabled but stopped and see it is still chatty.
I don't like the idea of needing the 20M work around in journald.conf -- I'd rather my journals only holding relevant info. The chatty services start to bury info it shouldn't.
It is an idle powered on Edison (no custom software running on the device) which will produce this logging traffic. Certainly it will do the logging only in network where mDNS is active. In our network we got some printers, a few dozen Mac's and a few dozen servers, they all have some mDNS registrations running, mDNS lookups are not so many. Even at home with only two Macs it is logging way to much.
I just tried avahi with the default options. Seems to be much quieter - just kind of tells it started
Not sure whether there are any benefits of mdns vs avahi (which also comes with mdns implementation as far as I understand).
I switched off mdns on one of my Edisons and replaced it with avahi.
Just checked: The avahi packages are already in AlexT's repo. So you might try those?
Helmut64, the repository mhahn is referring to can be found at repo.opkg.net/edison/repo/core2-32/
Thanks for the Info, I don't know if the avahi stuff uses an compatible API with mdnsd. There are methods to lookup and register mDNS entities, this communication goes via an UNIX domain socket in /var/run/mdnsd and I don't know if avahi is API compatible.
@deium, one question, I am new to the Edison, do you know how to pull and install a package,e.g. cronie on Yocto?
to stop a package I would use systemctl disable mDNS
there is a method to get an update to all of AlexT's repo located Edison Package Repo Configuration Instructions
or you can find the one .ipk and retrieve it with wget ie:
once you have a package run
opkg install pakage_name
For avahi, I would use the instructions in the configuration link above.
opkg install cronie_1.4.11-r0_core2-32.ipk
opkg remove cronie
No, I am still using the included mdnsd. We have also a own Bonjour server which I disabled to avoid a conflict with the included version. At present I clean once a date all journal log files.
I am surprised not more people have been impacted by this.. it is VERY annoying. after 6hrs of use (investigating why sketches won't upload in my hardware and software versions) "/" was 100% full with no activity in Bonjour... I concur way to chatty..
I had been testing with this edison on a full breakout card ardunio, against both win7 and MAC OSX10.10.1.. after encountering similar issues with the mini breakout in use (different edisons on different breakout cards.)..
everything else as per Helmut64's info..
I'll update after trying the above suggestions and see how that goes,,