[tszming]

Hi btmspox,

Firstly, thanks for your reply and your works on chef. I really appreciate it.

I think there is a difference between people who want free support & people who document a bug of a opensource project clearly in the hope of to improve the quality of that project - I hope I am in the latter case.

My reported issue can be easily fixed with some hacky workarounds, so I didn't bother with it and move on (As you can see I have never comment on that ticket). However, I still decided to create that ticket because I think the issue is easy to reproduce and will affect a lot of new comers to chef.

The issue is confirmed by others as well, one awesome commenter Florin Mihaila even provided a very detail analyse and solution to the issue.

For me, I would prefer if you can close the ticket if you think it is invalid, or mark as don't fix if resource is not allowed, rather than leaving as open and unanswered.

Of course, this is your project so I can't disagree with your preference, thanks anyway :)

[btmspox]

Always appreciate bugs being filed. I did a little pondering on the ticket the other day. Since we're using update-rc.d, we're likely talking about debian package install, which means that we could probably set the defaults correctly with update-rc.d, someone just needs to do the research and patch the init scripts or the debian packaging. So it's best for the bug to be open.

http://www.debian.org/doc/debian-policy/ch-opersys.html#s-sy... https://github.com/opscode/opscode-packages/tree/master/debi... https://github.com/opscode/chef/tree/10-stable/chef/distro/d...