I think it's openrc related because i never configured or used atmarpd.
It's something harmless because my network setup works fine.
My question is: What can i do to get rid of those messages or i just have to wait for the next openrc update? _________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

Last edited by Kollin on Mon Dec 10, 2012 3:49 pm; edited 1 time in total

I have the same errors at shutdown. Appeared with the upgrade to openrc 0.11.5.

Yea, but how to get rid of them ? _________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

I can't tell much more about this and don't think I will. Please move forward from there.
I am getting just fed up by the increasingly disgraceful way I am regularly told by my own system that I should no longer start / stop my processes as I want.

BTW, I appreciate how much a --quiet option obviously no longer means what... it used to mean... (to me) _________________

Openrc is definitely acting up recently _________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

I have had similar problems. Permissions on a number of subdirectories of /var/run now change on reboot and various daemons quietly fail (eg. sendmail - didn't get any email over the weekend until I discovered this).

I'm also having this problem with app-misc/uptimed, net-irc/inspircd, sys-process/atop, games-server/minecraft-server::java-overlay, net-im/prosody, and there's probably more stuff that's silently broken and I haven't noticed yet. These are just the ones that show up as crashed in rc-status that I've had to hack into a working state manually.

The OpenRC devs really need the concept of don't &$%@ing break working systems beating into their heads with a heavy stone.

Sadly sys-apps/openrc-0.11.6 does not solve the issue _________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

That worked for me, thanx! _________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

With respect, I don't consider removing linux-atm to be the solution to this problem.

I keep net-dialup/ppp and net-dialup/linux-atm installed on my system as a fallback in case my wireless router dies: I could then configure PPP/ATM to use an old ADSL modem instead.

In the meantime I do not start PPP/ATM. However I too am now seeing these "atmarpd.pid" warnings.

As far as I can tell the problem is that OpenRC is now trying to stop a service which it did not start. If that is the case then this is a real bug in OpenRC.

You are correct, may be you should consider opening a bug about this problem in bugs.gentoo.org_________________"Dear Enemy: may the Lord hate you and all your kind, may you be turned orange in hue, and may your head fall off at an awkward moment."
"Linux is like a wigwam - no windows, no gates, apache inside..."

The above link explains more about it, its not just a damon you can starup with init.d and it does its thing. you need configure ATM networking over IP to use it.

That is what i can gather about it anyway. I just removed tho atm use flag and updated world. Then emerge --depclean removed linux-atm package. At present i dont see any personal use for this networking technology, feel free to play though lol._________________When i look In-between white and black i see a rainbow of colours

I had set the atm USE flag only for iproute2 package in /etc/portage/package.use and not globally in /etc/portage/make.conf. I had the same messages mentionned above when my net.wlo1 wireless script was shutting down. The atm USE flag is not activated by default. I remove it and the messages disappear. Of course, emerge --depclean remove the atmarpd daemon after that.

I think the messages come from the iproute2 utilities when they are execute with atm support. According to euse, it's the only other package than the ppp one who can use this USE flag._________________Paul

As far as surfing the web i dont think it will benefit much. If you are connecting to a network that can optimise this technology then it is well worth getting it working. Just seting it up without using it could result in security issues in my opinion even if they have not been discovered yet.

If i actually had the time i would dig into this protocol deeper and see what i can find that uses it but life is short so ill put it on backburner. Feel free to hack it if you wish though, dont let me put you off :-p

Either way the reason you get this error is because the relevant programs required for ATM are not running. If someone out there actually has ATM runing feel free to share the info, saves us having to hack it lol.
More googling on ATM setup on linux might be a good place to start in getting it working.

I may revisit this thread again in a while depends if i get board after work and fancy hacking it me self at which point ill let you all know how to get it working of course.

You never know upstream might refine the code so it all starts and works semless in the near futur without having to hack it. Some would say that takes the fun out of it all but hey _________________When i look In-between white and black i see a rainbow of colours