search for: contrariwise

...part of AD that is not functioning for me at this point. I have also noticed some strange behavior when I browse to \\MYDOMAIN.LOCAL\ on the client and try to access a share called "profiles" that I created in /usr/local/samba/etc/smb.conf I get the error: "Element not found.", contrariwise, if I type in \\SERVER.MYDOMAIN.LOCAL or \\10.0.0.1\ and click on profiles I can get into the share, browse, and create/modify files just fine? Further when opening network neighborhood, \\MYDOMAIN.LOCAL is not what is loaded by default. I am hoping that this is all indicative of one or two admin...

...m here as this msg is going to a list. I'm not much of an expert with S-plus or R, and any help would be appreciated. Thanks in advance, Neil Neil Shephard Genetics Statistician ARC Epidemiology Unit, University of Manchester neil.shephard at man.ac.uk neil.shephard at mindless.com "Contrariwise, if it was so, it might be; and if it were so it would be; but as it isn't, it ain't. That's logic" - Tweedledee (Alice Through the Looking Glass)

> You have several hundred more Critical or Important security updates > outstanding. If that box touches the Internet in any way, it is likely > compromised. Just in the last 6 months there are 21 Important or > Critical updates. That is an important qualifier: *If* that box touches the Internet in any way. Although one might add that attacks on the LAN can be nastier since there

Hi, I am not sure if this is the right mailinglist (since I have an ogg problem not a vorbis)..... I am looking for some pointers on how to packetize an ogg stream. My idea is to use udp packets for transport, so I would need a way that would minimalize the impact of lost packets. Are there any code examples out there for this? Thanks, Jeroen p.s. Please cc me, I am not subscribed to this

Hi, I am not sure if this is the right mailinglist (since I have an ogg problem not a vorbis)..... I am looking for some pointers on how to packetize an ogg stream. My idea is to use udp packets for transport, so I would need a way that would minimalize the impact of lost packets. Are there any code examples out there for this? Thanks, Jeroen p.s. Please cc me, I am not subscribed to this

...ite.table() functions in the above script file??? Thanks again to all who offered help, and in anticipation of responses to this msg, Regards Neil Neil Shephard Genetics Statistician ARC Epidemiology Unit, University of Manchester neil.shephard at man.ac.uk neil.shephard at mindless.com "Contrariwise, if it was so, it might be; and if it were so it would be; but as it isn't, it ain't. That's logic" - Tweedledee (Alice Through the Looking Glass)

...there are production > environments where upgrading is a huge pain or outright impossible. updating vs upgrading? and such "impossible" cases are rare compared to the majority of EL OS installations. Saying that because the implicitness should be systems in a current state and not contrariwise. > Where any upgrades need to undergo a rigorous QA process. the solution: automation > Where an outdated environment including equally outdated production > tools needs to be maintained, on the chance e.g. that a customer > return requires reworking an old part. I would consid...

Hi everybody, I'm looking into replacing the linked lists in tinc with balanced trees. Using balanced trees will greatly improve performance for medium to large VPNs. As I see it, there are several options: 1) Use tsearch()/twalk()/etc functions from glibc. + It is in a very standard library - It relies solely on callback functions, which sometimes results in ugly, awkward code (I

Hi John, I'll read your email with greater care along the week, but I have added a page on the wiki to help us organise our thoughts. http://wiki.llvm.org/Exception_Handling I'll change it as I go reading your email, but for now, I've separated into each of the requirements you said. New ones could be added, existing ones merged, but the most important is to add more complete

...l goal to make LLVM IR capable of supporting a wider range of unwinders than it currently can — at a gloss, non-resumptive EH with a single, non-reentrant landing pad per region and LSDA layout approximating what's consumed by __gxx_personality_v0 — then that touches on almost everything else. Contrariwise, if we're only really interested in finding a better fix to the current IPO problems, then maybe we can get away with very modest changes. And it's okay to have limited goals! I personally don't; I think we should aim to get the IR design good enough to support crazy resumptive lang...

...environments where upgrading is a huge pain or outright impossible. > > updating vs upgrading? > > and such "impossible" cases are rare compared to the majority of > EL OS installations. Saying that because the implicitness should > be systems in a current state and not contrariwise. > >> Where any upgrades need to undergo a rigorous QA process. > > the solution: automation And a) the manager who made the decision to not upgrade needs to be made aware of a) the dangers of *not* upgrading; b) the minimal risks up an upgrade (security & bugfixes), and c) need...

Since it looks like we're going to start discussing changing the EH representation again, I think it would be a very good idea to first review the core requirements we have of the exceptions IR. Mostly, here, I'm taking the major exceptions implementations I have direct knowledge of --- zero-cost DWARF-based libUnwind with the default GCC personalities, builtin_sjlj-based libUnwind with

...%u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio # # The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a <VirtualHost> # container, they will be logged here. Contrariwise, if you *do* # define per-<VirtualHost> access logfiles, transactions will be # logged therein and *not* in this file. # #CustomLog logs/access_log common # # If you would like to have separate agent and referer logfiles, uncomment # the following directives. # #CustomLog logs/referer_log r...

...s %b" common LogFormat "%{Referer}i -> %U" referer LogFormat "%{User-agent}i" agent # # The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a <VirtualHost> # container, they will be logged here. Contrariwise, if you *do* # define per-<VirtualHost> access logfiles, transactions will be # logged therein and *not* in this file. # #CustomLog logs/access_log common # # If you would like to have agent and referer logfiles, uncomment the # following directives. # #CustomLog logs/referer_log referer #Cu...