Hacker News new | past | comments | ask | show | jobs | submit login

> No, how did you accidentally write to /etc/init.d?

Let me quote again, with a finer slicing:

> I went through all of the above because some real machines hit this for some reason. I don't have access to them




So you don't know? Gotcha.


And you apparently never managed anything in production.

Have you ever heard of "reproducing a problem"?


I've never seen anything write to /etc/init.d in production (or anywhere actually), which is why I asked for the root cause.


Without, all the time, bothering to read the article, and asking here something that no-one here could know, because it's not in the article. If you really wanted to know, you could have mailed the author.

Boy, do you deserve these downvotes.


How do I get downvote access? I'm jelly.


Get a high enough score. Also don't use words like jelly. HN doesn't like reddit's tendency to use funny memes etc.


"jelly" is a word, not a funny meme. (Also, it's Hacker News, not Not-Reddit News.)


Thank you.


From the article Upstart is watching /etc so the example might have used /etc/init.d just to illustrate it

But yes, it is really strange. This usually means some weird proprietary tools


I'm a bit out of the loop on this stuff, but isn't this kind of thing (bulk-rewriting stuff in /etc) exactly what configuration management systems do in their normal operation?


I don't have a chef/puppet/etc system handy at the moment, but could this possibly be the result of someone setting a file immutable, with the chef recipe dealing with that bit of the filesystem changing, causing chef to repeatedly trying to apply a changeset?


The author indicates the watcher also follows /etc, so any files written there could cause this as well.


That's the point.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: