search for: yetanoth

...', this would be okay. This would your > allow your domain clients (winpc.ad.mydomain.com, for instance) to ask > the DC for the dns data for 'another-winpc.ad.mydomain.com' and the DC > would reply with the data. However, if 'winpc' asked for the data for > 'yetanother-winpc.mydomain.com', then the DC should realise 'I do not > know this' and ask the dnsmasq server. > > Rowland > > > In your case the lookup for yetanother-winpc.mydomain.com shouldn't even hit the DC as dnsmasq will handle it directly as all lookups go via...

...se that one solution here is to just not check the syntax of the template with erb (as it works absolutely fine with a single %).. However, it feels a little bit broken or (quite possibly) I''m missing something obvious so would be good to get some feedback. Thanks in advance! -- Tim tim@yetanother.net -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com. For more options, visit t...

That mean for example if my domain resolve xxxxx.testing.mydomain.com the dnsmasq should NOT resolv xxxxxx.mydomain.com this is in ascending way ? Another way to expose: We set dnsmasq+dhcp to set clients that the only DNS server is samba DC on the domain name mysubdomain.mydomain.com DC for example resolv server1.mysubdomain.mydomain.com right, now if a client as for a

...problem: --------------------------------- *** compat.c Sat Nov 4 21:42:36 2000 --- compat.c.new Fri Dec 22 11:10:52 2000 *************** *** 66,71 **** --- 66,74 ---- { "MindTerm", 0 }, { "^2\\.1\\.0 ", SSH_BUG_SIGBLOB|SSH_BUG_HMAC| SSH_OLD_SESSIONID }, + /* yetanother 2.1.0 */ + { "^2\\.1\\.0.pl2 ", SSH_BUG_SIGBLOB|SSH_BUG_HMAC| + SSH_OLD_SESSIONID }, { "^2\\.0\\.", SSH_BUG_SIGBLOB|SSH_BUG_HMAC| SSH_OLD_SESSIONID| SSH_BUG_PUBKEYAUTH|SSH_BUG_X11FWD },

...ies are always on a line by themselves. Finding the "if (CONDITION" line should be relatively easy. The difficulty for me is identifying the matching curly bracket - there are often paired brackets within the block of code: if (CONDITION) { ... if (SOMETHINGELSE) { } if (YETANOTHER) { } } <- this is the bracket that I need to match There are also instances in which the entire block occurs on one line: if (CONDITION) { ...} else invisible() or if (CONDITION ... else invisible() Of note, I can remove the "else invisible() statements if they are probl...

...indeed otherpackage::otherfun I get, ie I do not get a different function, also called otherfun, that for one reason or another exists in memory and is found as R works its way up the chain of enclosing environments. Usually the concern is about an identically named but different `otherfun` from `yetanother` package that has been loaded, or that the user has defined themselves in their globalNamespace. But in the motivating example for my case, I wanted to ensure I got the otherfun from version >= 2.0 of `otherpackage`, and in particular, I did **NOT** get `otherpackage(version 1.0)::otherfun`...