On Wed, Jan 27, 2016 at 09:47:04PM +0100, Antoine Jacoutot wrote: > > > rc.d framework is so nice... not sure if this is nice way but it > > > works. Maybe check for existing rtable is not great. > > > > If I see this correctly you add a foo_rtable variable to rc.conf.local. > > I think there is some drawback to this solution. > > You can only have one daemon running in one rtable at a time > > I often run things like sshd in multiple rtables / rdomains in which > > case I would have to copy the sshd rc.d script and fiddle a bit here and > > You don't have to copy it, just link it (so you get updates to the original > script) and add ssht2, ssht3... to pkg_scripts. > But yeah, it's not an obvious road and that's why I warned not to hold any > breath ;-) > > > there. I would prefer if we would have a rc.conf file specific for a > > rtable. Also it is not possible to start daemons with different flags. > > Hmm. Can you extend on that? > We should be able to make something like this work: > > # ln -s /etc/rc.d/sshd /etc/rc.d/sshdt2 > # rcctl enable ssht2 > # rcctl set ssht2 flags -f /etc/ssh/wunder_config
Aha, that is what I was looking for. So if this works I'm totally happy :) Didn't know that you can just symlink rc scripts and everything will work. > > Non the less I think this is a move in the right direction. > > It is. It's basically the last obvious situation rc.d does not handle besides > what was mentioned today (multiple httpd, relayd, ...). > Good thing we have rc.local ;-) This is what I currently do and I tend to forget about it and restart stuff in the wrong rdomain. > Anyway, I've been pretty busy lately but I think that's something I'd like to > investigate during our upcoming hackathon a couple months from now (it's too > late for this release anyway). > I will for sure give this a try on my rdomain-ed firewall at home. -- :wq Claudio
