similar to: flakey things samba 2.2.2

Displaying 19 results from an estimated 19 matches similar to: "flakey things samba 2.2.2"

1998 Jul 17
13
connection problem
I have two identical AIX v4.2 machines. One of them was vendor installed, and I installed the OS on the other one. I am successfully running Samba-1.9.18p4 on the vendor installed OS, but I cannot seem to get any Win95 clients to browse on my other machine (Explorer hangs on the Win95 client). I have performed all of the tests in DIAGNOSIS.txt. All of the tests work except for number 7. I can
2006 Aug 03
1
Very strange - AJAX is flakey when I uploaded my site
The weirdest thing is happening. I have an ajax uploading call, and after I uploaded it, every part of the controller will work except the ajax call. The Ajax call is to a javascript function that is in one of my js file. Ive confirmed that the controller runs all the way till the render :update. Then, there I have: responds_to_parent do render
2008 Jun 30
1
access of WML site through cell phone seems flakey
I just started a new subdomain on hosting rails. I launched it a couple of days ago. It is a site that can render onto mobile devices using WAP/WML or through a regular browser. It seems flaky with the mobile cell phone access, because sometimes it works and sometimes it stops working for several hours and then it seems like it''s fine again, with a regular browser it seems ok, though
2015 May 11
0
CentOS 7 MATE flakey mouse
I just realized that more than MATE Terminal is affected. For example, if I'm using firefox on a long web page, click the scrollbar and quickly scroll through the page, then sometimes it behaves like after a bit I've released the mouse button: Instead of scrolling, the mouse (which is now outside of the scroll bar area) starts highlighting text instead.
2015 May 11
1
CentOS 7 MATE flakey mouse
On Mon, 11 May 2015 14:42:36 -0600 Devin Reade wrote: > I just realized that more than MATE Terminal is affected. For > example, if I'm using firefox on a long web page, click the scrollbar > and quickly scroll through the page, then sometimes it behaves like > after a bit I've released the mouse button: Instead of scrolling, > the mouse (which is now outside of the scroll
2015 May 12
0
CentOS 7 MATE flakey mouse
On Mon, May 11, 2015 at 02:38:21PM -0600, Devin Reade wrote: > I'm using the MATE desktop (via 'yum groupinstall "MATE Desktop"') on > CentOS 7. I'm finding the mouse to be rather flakey in the sense > that: > - in MATE Terminal, clicking on text and dragging the mouse (in order > to highlight the text and copy it to the X cut & paste buffer) will
2003 Oct 08
1
BudgeTone 102 flakey sound
I have experienced lots of apparently dropped packets (in other words, lots of short interruptions of what the other party tries to tell me) with a GS102 and chan_capi. The GS102 is connected through a lightly-loaded switch directly connected to the * server, so bandwidth/latency shouldn't pose a problem. Funny thing is that the switch indicates 10mbit on the GS102 port - is that correct?
2015 May 11
4
CentOS 7 MATE flakey mouse
I'm using the MATE desktop (via 'yum groupinstall "MATE Desktop"') on CentOS 7. I'm finding the mouse to be rather flakey in the sense that: - in MATE Terminal, clicking on text and dragging the mouse (in order to highlight the text and copy it to the X cut & paste buffer) will sometimes drop the highlight (thus not copying anything), or stop and
2003 Oct 07
2
Dynamic registration to flakey for production system
Three days after launching our * system with 20 GS phones, I have finally had to give up on dynamic registration. The phones keep dissappearing from the sip peers list, even if just sitting idle. Either I spend half my time re-booting phones to get them registered, or the extension appears busy to outside callers and people get really irritated. Even setting the registration interval to 5
2001 Dec 13
3
behaviour of ssh/scp over flakey links - timeout/retry?
I'm using OpenSSH's ssh and scp to back up some remote machines, roughly as follows : ssh remote-host "tar up a few dirs" scp remote-host:tarfile local-repository On the whole, as I'd expect, this works just fine. But .. sometimes the link is a bit dodgey (for lack of a more explicit term, this being a polite list :) ) Can anyone tell me how ssh and scp timeout and retry,
2020 Sep 01
2
Flakey failure on clang-ppc64le-linux-multistage
Seems there were a couple of correlated failures that appear to be flakes on this buildbot recently: green: http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/13974 red: http://lab.llvm.org:8011/builders/clang-ppc64le-linux-multistage/builds/13975 (target-override.c during stage 1, seems to be missing the directory/symlink it just created) red:
2020 Sep 02
2
Flakey failure on clang-ppc64le-linux-multistage
Well, I am at my wit's end. I have copied over the script and directories for this test case and run it a few million times. First I was running one at a time, then I switched to kicking off 1000 at a time. All the while, the bots continued to run on the same machine. The script never failed even once. I am not sure if this has something to do with Python as part of llvm-lit or what is going
2020 Sep 04
2
Flakey failure on clang-ppc64le-linux-multistage
Thanks everyone for this discussion. Turns out that in my effort to make it possible to run multiple instances of this script in parallel, I inadvertently hid the issue. I made each instance use a directory that has $1 appended to the name and the wrapper script provided a unique value with $LINENO. :( MaskRay, thanks for fixing the problem. All the PPC bots are back to green now. On Thu, Sep 3,
2020 Sep 03
2
Flakey failure on clang-ppc64le-linux-multistage
Sure. I didn't use lit or ninja. I simply copied the script produced by lit (/home/buildbots/ppc64le-clang-multistage-test/clang-ppc64le-multistage/stage1/tools/clang/test/Driver/Output/target-override.c.script) into a temporary directory (along with a deep copy of the build directory). I modified the paths in the script to point to the temporary directory. Then I ran the script in a loop. For
2020 Sep 03
2
Flakey failure on clang-ppc64le-linux-multistage
This is likely due to a race condition (%T is a shared parent directory). I'll put up a patch to fix it. On Thu, Sep 3, 2020 at 10:00 AM David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Is the machine running any jobs in parallel? Would it be worth trying running lit in the loop, rather than the script? (perhaps lit's doing something interesting) or maybe the
2020 Sep 03
3
Flakey failure on clang-ppc64le-linux-multistage
Should be fixed by https://reviews.llvm.org/D87103 Shall we consider deprecating(emitting a warning)/removing %T from lit? lldb, lld/COFF and clang-tools-extra are the three major users of %T. There are a few other %T in other places but there are not too many. We will also investigate whether other projects using lit are using %T. On Thu, Sep 3, 2020 at 11:25 AM David Blaikie <dblaikie at
2020 Sep 03
2
Flakey failure on clang-ppc64le-linux-multistage
https://llvm.org/docs/CommandGuide/lit.html already lists %T as "parent directory of %t (not unique, deprecated, do not use)". See also https://reviews.llvm.org/D35396 On Thu, Sep 3, 2020 at 3:37 PM David Blaikie <dblaikie at gmail.com> wrote: > Yeah, I think I'd be up for considering deprecation of %T due to the risk > of race conditions/conflicts between tests. %t
2004 Aug 04
3
Winbind being flakey
After some more screwing around with leaving and rejoining the ADS domain I was finally able to access a share with "valid users =" set to a domain group I was a member of. The _only_ change I made after this was to add yet another group to the valid users on the share and restart samba...after that I could no longer access the share. I removed the additional group, restarted samba and
2020 Sep 03
2
Flakey failure on clang-ppc64le-linux-multistage
I think that was maybe the discussion on https://reviews.llvm.org/D78245 On Thu, Sep 3, 2020 at 6:22 PM Robinson, Paul <paul.robinson at sony.com> wrote: > I have a vague memory that libcxx wanted it for something, and claimed it > would be hard to work around not having it. > > Anyone else remember that? I can’t dredge up the details, sorry… > > In any event, a separate