search for: nightmarish

..., are there any "best practices" for backing up critical Samba files in an effort to make recovery "easier?" I have read a multiplicity of opinions offered to me by the oracle at Google, but am wondering if the Samba community has some established best practices. It was sort of nightmarish having 50+ users sitting around waiting for their network to be fixed, and I'd rather not go that way again so feel free to tell me how stupid it was to not have addressed this before. ;-) Samba: 3.6.6 Ubuntu: 10.4.4 LTS Kind Regards, Chris

...y, April 07, 2011 11:23:51 AM Brunner, Brian T. wrote: >> AIUI: In previous releases, RH distributed source + patches. ?Starting >> 6.0 RH releases patched source. ?This makes backing out a patch, or >> backporting patches from future development in Fedora (e.g.) far more >> nightmarish than before. > > This one doesn't impact the CentOS core rebuild. ?It would/could impact CentOSPlus. Yes, it _could_ affect the centosplus kernel. This point was addressed early on when RHEL-6 was released back in Nov 2010. See: http://bugs.centos.org/view.php?id=4586 Point 2 (note 120...

Hi. I've tried Samba 3.4.3 and it upgraded my passdb.tdb file. After testing I concluded that I'm not going to upgrade to 3.4.3 yet, because 'getent passwd' was broken in recent BlastWave Solaris packages: http://wiki.blastwave.org/forum/viewtopic.php?f=5&t=447&start=0 Now, after I downgraded the Samba back to 3.0.32, client connections started to malfunction. I saw

...mu VFB due to https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=718620 = the event channel issue where the dom0 and domU are using different vcpus while talking to each other http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00004.html this could possibly be sorted with a nightmarish hack that maps all vcpus onto one cpu on shutdown time by sshing into dom0. One would have to ensure the mapping is OK again after a reboot. err. you can imagine how much I "like" this idea. = domU kernel: yet untested, I hardly have any chance of updating it, rather would need to backpo...

For most cases, I''ve got search working in Rails as follows: ## controller: term = params[:search][:term] @results = MyModel.find_by_contents "#{term}*" The ''*'' character is appended to the search term so that searches match anything that begins with ''term''. For the most part, this is great, but let''s say term is equal to

On May 10, 2017 9:14 PM, "Hal Finkel" <hfinkel at anl.gov> wrote: On 05/10/2017 10:36 PM, Zachary Turner via llvm-dev wrote: It's hard to say. By definition it appears undefined (in the sense that the TS literally does not define it), but on the other hand it is a TS and this issue would (hopefully) come up and be specified before it made it to standardization. You mean

I'm implementing a more efficient version of the Xen iret paravirt_op, so that it can use the real iret instruction where possible. I really need to get access to per-cpu variables, so I can set the event mask state in the vcpu_info structure, but unfortunately at the point where INTERRUPT_RETURN is used in entry.S, the usermode %fs has already been restored. How would you feel if we changed

I'm implementing a more efficient version of the Xen iret paravirt_op, so that it can use the real iret instruction where possible. I really need to get access to per-cpu variables, so I can set the event mask state in the vcpu_info structure, but unfortunately at the point where INTERRUPT_RETURN is used in entry.S, the usermode %fs has already been restored. How would you feel if we changed

Hi, Using the %L macro in smb.conf is for me *very* usefull, I can setup as many logical servers as I need and that's great : no need for new machines, I can switch logical servers back and forth, it's a kind of System Administrator dream :-) *But* I've discovered a problem with the %L macro in a subnetted environment : - "hermes" is a Samba 1.9.18p10 server on a hpux

Hi All After upgrading to 7.2, I'm getting an immediate kernel panic on boot Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine How can I go about diagnosing the problem here? thanks Duncan

Hello, After researching the subject on the internet I concluded that Samba should take into account Unix file acls. During my tests I found the opposite. Only Unix file mode bits are respected, and file acls are ignored. If my initial assumption is correct and Samba do respect Unix file acls, then I am doing something wrong. Please see the setup below and point to what I am doing wrong.

...Mongrel BUGS Mascot! To: mongrel-users at rubyforge.org Message-ID: <eef0b5c0606300023g51e99d82ieb6895b8aededd1 at mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" +1 OSCAR He''s the only on who''s not going to give me nightmares (and bugs are nightmarish enough ;-) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060630/61d09261/attachment-0001.html ------------------------------ Message: 5 Date: Fri, 30 Jun 2006 00:43:18 -0700 From: "Jason A. Hoffman&q...

I got tired of restarting my puppetmaster when it stopped responding and finally switched to mongrel last night. When running under mongrel, what sort of concurrent connection rates are people able to get? I dont know how many individual puppetmaster processes I should spawn, or how to tell when I should span more. Perhaps I need more than two, because this morning I had a look at how

I''m pinging the list to see if anyone is working on an open-source e-commerce engine based on Rails yet - something like OSCommerice I guess. Anyone? Is there interest out there for such a thing? I have such a product which has been extracted from real world code. It currently runs 3 production rails sites in various shapes and forms, implemented as a rails engine. Basic feature list: -

Bradley Taylor shot me this *goldmine* of ugly ugly ugly dogs: http://www.sonoma-marinfair.org/uglydogvote.shtml I *have* to use one of these for the Mongrel BUGS Mascot. He''ll go on our bug list page and replace the little beetles on the left. Pick the dog you think best represents a lovable but defective pooch and reply to this with your +1. Let the voting begin! -- Zed A. Shaw

...virtual address interpretation. + * We originally used to use segments so the Guest couldn't alter the + * Guest<->Host Switcher, and then we had to trim Guest segments, and restore + * for userspace per-thread segments, but trim again for on userspace->kernel + * transitions... This nightmarish creation was contained within this file, + * where we knew not to tread without heavy armament and a change of underwear. + * + * In these modern times, the segment handling code consists of simple sanity + * checks, and the worst you'll experience reading this code is butterfly-rash + * from f...

...virtual address interpretation. + * We originally used to use segments so the Guest couldn't alter the + * Guest<->Host Switcher, and then we had to trim Guest segments, and restore + * for userspace per-thread segments, but trim again for on userspace->kernel + * transitions... This nightmarish creation was contained within this file, + * where we knew not to tread without heavy armament and a change of underwear. + * + * In these modern times, the segment handling code consists of simple sanity + * checks, and the worst you'll experience reading this code is butterfly-rash + * from f...

...virtual address interpretation. + * We originally used to use segments so the Guest couldn't alter the + * Guest<->Host Switcher, and then we had to trim Guest segments, and restore + * for userspace per-thread segments, but trim again for on userspace->kernel + * transitions... This nightmarish creation was contained within this file, + * where we knew not to tread without heavy armament and a change of underwear. + * + * In these modern times, the segment handling code consists of simple sanity + * checks, and the worst you'll experience reading this code is butterfly-rash + * from f...

...virtual address interpretation. + * We originally used to use segments so the Guest couldn't alter the + * Guest<->Host Switcher, and then we had to trim Guest segments, and restore + * for userspace per-thread segments, but trim again for on userspace->kernel + * transitions... This nightmarish creation was contained within this file, + * where we knew not to tread without heavy armament and a change of underwear. + * + * In these modern times, the segment handling code consists of simple sanity + * checks, and the worst you'll experience reading this code is butterfly-rash + * from f...

On Sun, Mar 9, 2014 at 10:51 AM, Marcin Slusarz <marcin.slusarz at gmail.com> wrote: > [ 326.168487] ====================================================== > [ 326.168491] [ INFO: possible circular locking dependency detected ] > [ 326.168496] 3.13.6 #1270 Not tainted > [ 326.168500] ------------------------------------------------------- > [ 326.168504] ldconfig/22297 is