Displaying 20 results from an estimated 5000 matches similar to: "samba 3.0.3 + windows backup software = strange issue"
2014 Feb 10
2
can not see public mailbox
Hello,
I'm running Dovecot2 and trying to set up public mailboxes. I've got a
virtual user system set up with postfix and using MySQL
authentication. I'm wanting to create several public mailboxes for
shared messages. I've followed the wiki and have the public folder
created. I've got a folder /home/vmail/public/public1 public1 being
the maildir of the public mailbox.
I can
2019 Apr 25
1
Samba 4 write lock problem with MS Word
I'm getting "access denied" with one particular samba 4 home directory NFS
share. But only with Microsoft Word, Excel and PowerPoint. If I edit an
RTF file in wordpad or notepad and save it back to the samba home share it
works. But I get "access denied" if I'm using Word. Also, no problems with
WordPerfect.
On the same NFS mount point I have several Samba shares. Lets
2007 Mar 06
2
parse error with if else (PR#9551)
Full_Name: Stephanie MAHEVAS
Version: 2.4.1
OS: Windows NT
Submission from: (NULL) (134.246.55.50)
the two following instructions provide a synthax error :
if ( 5 > 4 ) cat("ok1")
else cat("ok2")
and
if ( 5 > 4 ){ cat("ok1")}
else cat("ok2")
whereas these ones don't
if ( 5 > 4 ) cat("ok1") else cat("ok2")
and
if (
2009 Jul 07
0
Protection stack overflow when calling setGeneric()/setMethod() from within .onLoad()
Hi list,
Calling setGeneric()/setMethod() from within the .onLoad() hook
of MyPkg package produces the following error:
> gctorture(TRUE)
> library(MyPkg)
.onLoad(): ok1
.onLoad(): ok2
Error : protect(): protection stack overflow
Error : .onLoad failed in 'loadNamespace' for 'MyPkg'
Error: package/namespace load failed for 'MyPkg'
This is with
2016 Jan 28
2
Dovecot (director, lmtp) IPv4/IPv6?
Hello,
I'm build system with two director/proxy and dual stack network (or
IPv6-only local services)
http://wiki2.dovecot.org/Director say "This also means that a single
director ring must use either IPv4 or IPv6 addresses, but not both at
the same time." OK
All servers have 2 interface (public and local network), and all dual
stack IPv4/IPv6, imap/pop (mail) and lmtp (mx) proxy run
2006 Dec 05
1
vorbis-tools-1.1.1 build mechanism stubbornly refuses to build with FLAC, ogg123, speex
Hello,
I am trying build vorbis-tools-1.1.1 in the framework of my tool (see signature).
The essence of the tools is that it builds and install everything locally, and, of
course, it uses the available mechanisms to specify search paths for both headers
and libraries; the tool first builds dependencies abd then the target itself.
So, for example, 'configure' for vorbis-tools-1.1.1 is
2007 Nov 25
1
vorbis-tools-1.1.1 build fails during linking
Hello All,
even though 'configure' for vorbis-tools-1.1.1 is OK 'make' fails - please see
the command line and error messages below.
Aby ideas why this happens ?
Thanks,
Sergei.
The failing command line and error messages:
99 gcc -O20 -ffast-math -fsigned-char -o oggenc oggenc.o audio.o encode.o platform.o
resample.o
2001 Jun 01
2
Admin question[s]
Hello,
I'm brand new to this streaming stuff so please bear with me.
I have installed and am running icecast 1.3.10, ices latest version:
0.0.1 beta5
and/or shout 0.8.0. No major problems with the exception of the
clients like to drop off
[and I see this problem posted before but didn't see any fix for it].
Btw... this is on Linux Slackware 7 operating system.
My question is
2011 Nov 30
0
[LLVMdev] [llvm-commits] Bottom-Up Scheduling?
Andy,
Thank you for the extended and prompt answer. Let me try to summaries my
current position so you (and everyone interested) would have a better view
of the world through my eyes ;)
1) LLVM first robust VLIW target is currently in review. It needs for
scheduling strategy/quality are rather different than what current
scheduler(schedulers) can provide.
2) My first attempt in porting
2012 Sep 03
2
[LLVMdev] Assert in LiveInterval update
Hi Sergei,
I just fixed the broken test case for PR13719 with r163107, but from the
debugging output you've posted it suspect it won't fix your test case.
Your analysis looks good - findLastUseBefore(..) doesn't appear to be
handling physregs. I'm surprised that isn't causing more failures. I'll see
if I can find a failing case in the LLVM test-suite (it's been a
2013 Jan 29
1
[LLVMdev] Apparent indeterminism in PreVerifier
Is there a test case that you can share ?
On Jan 29, 2013, at 9:24 AM, Sergei Larin <slarin at codeaurora.org> wrote:
> Nadav,
>
> Thanks for the quick response. By now I am convinced that the given loop
> ends up vectorized with enough difference to cause bad things later on, but
> I have not found the exact cause yet. To continue with my work I'll have to
>
2009 May 03
12
DNAT Question
Hi list,
I have a shorewall installed on 2 interfaces which also has multiple
static public IP. Let''s say I have 1.2.3.4 and 1.2.3.5. I have assigned
nat with:
1.2.3.4 eth0 11.22.33.4 no no
But then I have a situation where I need 11.22.33.44 to connect to a
host in the net zone and appears also to be 1.2.3.5 not only 1.2.3.4.
How to do it? TIA
Willy
2014 Jun 13
2
[LLVMdev] Looking for a fix to memory leak in DWARF support
Eric,
Let me clarify it a bit... without type uniqueing for LTO + debug will I have a highly inefficient IR representation or incorrect debug info? If debug info for LTO is known to be non-useful or ambiguous or flat wrong - there is no point in fixing its emission... or will it still be practical and if I manage to improve it somewhat the customer will still have some value-add by using it?
2012 Mar 29
0
[LLVMdev] VLIWPacketizerList: failing to schedule terminators
Tom,
I do not have your call stack, but packetizer calls
ScheduleDAGInstrs::buildSchedGraph to create dependency model. If this is
the first time you use the new MI sched infrastructure (like your target has
not implemented misched yet) there might be some work needed to implement
couple target hooks. isSchedulingBoundary is one of them. Also try to
disable that assert and see what happens. It
2013 Jan 29
0
[LLVMdev] Apparent indeterminism in PreVerifier
Nadav,
Thanks for the quick response. By now I am convinced that the given loop
ends up vectorized with enough difference to cause bad things later on, but
I have not found the exact cause yet. To continue with my work I'll have to
simply turn off vectorization for now, but I will come back and investigate.
Again, there is some indeterminism in order of PHIs processing somewhere.
I'll
2003 May 08
2
tinc/src net.h,1.9.4.57,1.9.4.58 net_packet.c,1.1.2.29,1.1.2.30
aG93IHRvIGNoZWNrb3V0IHRoZSBsYXN0IGRldmVsb3AgdGluYz8gKENWUyxjb21wbGllIGFibGUp
DQo=
Tinc: Discussion list about the tinc VPN daemon
Archive: http://mail.nl.linux.org/lists/
Tinc site: http://tinc.nl.linux.org/
2012 Aug 13
0
[LLVMdev] MI bundle liveness attributes
Andy,
Yes, this is what Arnold has suggested also, and from this point it looks
like it should work, but it will require parsing the bundle every time we
care to know whether this is a real use or a conditional def. This might
become awkward... but I guess I should provide a better use case to prove my
point.
Sergei
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum.
>
2012 Aug 31
0
[LLVMdev] Assert in LiveInterval update
Lang,
I think I am getting closer to understanding this. The findLastUseBefore()
should probably look something like this:
// Return the last use of reg between NewIdx and OldIdx.
SlotIndex findLastUseBefore(unsigned Reg, SlotIndex OldIdx) {
SlotIndex LastUse = NewIdx;
if (TargetRegisterInfo::isPhysicalRegister(Reg)) {
for (MCRegUnitRootIterator Roots(Reg,
2004 Aug 06
0
Admin question[s]
welcome to the list.
Check the archives.
There you will find about one newbie a month minimum discovering that the
widely distributed and still available shout package version 0.8.0
is actually deprecated and highly broken in exactly the manner you
describe.
On Thu, 31 May 2001, Kevin Brouelette wrote:
> Date: Thu, 31 May 2001 21:34:55 -0700
> From: Kevin
2011 Nov 14
0
[LLVMdev] alias analysis in ScheduleDagInstr class
We observed exact same problem, and I did put in place a mechanism to
recognize and break such false dependencies right before pre-RA scheduler
(in DAG->DAG lowering), but the immediate observed effect for our back end
was performance reduction, since none of the current schedulers were capable
of dealing with newly presented parallelism in BB (resulted in high reg
pressure and