similar to: Fw: Samba S/w Configuration

Displaying 20 results from an estimated 900 matches similar to: "Fw: Samba S/w Configuration"

2008 Jan 24
2
Problems when compiling MFC application
<table cellspacing='0' cellpadding='0' border='0' ><tr><td style="font: inherit;"><font size="2">Dear All,</font><br> &nbsp;<br> <font size="2">&nbsp;&nbsp;&nbsp;&nbsp; This is my first post on the wine organisation mailing lists, i would like to inform all of you i am using
2017 Sep 25
0
Potential infinite loop in MemorySSAUpdater
We should only add phis that were newly inserted, not ones that were already found. There are two cases we will hvae inserted phis: Part of the recursive call, or right in this function. The easiest way to differentiate new phis from old ones is whether they have 0 operands. I expect the attached will fix it. If not, please file a bug with reproducible IR. On Sun, Sep 24, 2017 at 11:40 PM,
2007 Jun 24
1
Divided by Zero Error Speex-dev Digest, Vol 34, Issue 12
Hi, I am getting the same problem of divided by zero while decoding in the function multicomb(). I am using fixed point speex code. Can anybody please tell me the solution for it. -----Original Message----- From: speex-dev-bounces@xiph.org [mailto:speex-dev-bounces@xiph.org] On Behalf Of speex-dev-request@xiph.org Sent: Tuesday, March 13, 2007 12:30 AM To: speex-dev@xiph.org Subject: Speex-dev
2017 Sep 23
2
Potential infinite loop in MemorySSAUpdater
Hi, Can some one explain the intended behaviour of following loop in void MemorySSAUpdater::insertDef(MemoryDef *MD, bool RenameUses) function. while (!FixupList.empty()) { unsigned StartingPHISize = InsertedPHIs.size(); fixupDefs(FixupList); FixupList.clear(); // Put any new phis on the fixup list, and process them FixupList.append(InsertedPHIs.end() - StartingPHISize,
2017 Sep 25
2
Potential infinite loop in MemorySSAUpdater
I understand that changing the starting element to “InsertedPHIs.being() + StartingPHISize” it will be finite but given that InsrtedPHIs is finite. I have a case where one element(same element is appened to InsertedPHIs) is added to InsertedPHIs every time fixupDefs is invoked. I traced the issue why this was happening. template <class RangeType> MemoryAccess
2010 Apr 05
2
Regarding problem with encoding / decoding
Hi, Tank you for your reply. I have tried the sample programs given the manual and done encoding and decoding a wave file. That is working fine. I have already read the manual and API reference. But this problem did not occured with the wave file encoding/decoding. While capturing the data from MIC and encoding/decoding is giving this problem. Thanks and Regards, Vijender Reddy, -----
2017 Sep 23
0
Potential infinite loop in MemorySSAUpdater
On Sat, Sep 23, 2017 at 9:55 AM, Godala, Bhargav-reddy < Bhargav-reddy.Godala at amd.com> wrote: > > With regards > Bhargav Reddy Godala > Software Engineer 2 > Bangalore, India > E-mail: Bhargav-reddy.Godala at amd.com Ext 30678 > > > > On 23-Sep-2017, at 9:27 PM, Daniel Berlin <dberlin at dberlin.org> wrote: > > > > On Sat, Sep 23, 2017 at
2019 Dec 30
0
Issue running Dovecot in Docker Container
Aki, This image doesn't have a director service, just the dovecot is running. Marc, I'm running the docker container in a privileged mode and it doesn't seem to have any issues reaching out to the outside network. I will try running with default config and see what fails. Thanks & Regards, Naveen On Mon, Dec 30, 2019 at 4:16 PM Aki Tuomi <aki.tuomi at open-xchange.com>
2017 Jul 13
0
[Gluster-devel] gfid and volume-id extended attributes lost
Ram, I sent https://review.gluster.org/17765 to fix the possibility in bulk removexattr. But I am not sure if this is indeed the reason for this issue. On Mon, Jul 10, 2017 at 6:30 PM, Ankireddypalle Reddy <areddy at commvault.com> wrote: > Thanks for the swift turn around. Will try this out and let you know. > > > > Thanks and Regards, > > Ram > > *From:*
2017 Jul 07
0
[Gluster-devel] gfid and volume-id extended attributes lost
3.7.19 Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] Sent: Friday, July 07, 2017 11:54 AM To: Ankireddypalle Reddy Cc: Gluster Devel (gluster-devel at gluster.org); gluster-users at gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost On Fri, Jul 7, 2017 at 9:20 PM, Ankireddypalle Reddy <areddy at
2019 Dec 30
0
Issue running Dovecot in Docker Container
Hi Marc, I can see the processes are running as a root in container environment. Do you think that still have issues ? Here is the processes running inside container: bash-4.2# ps -ef UID PID PPID C STIME TTY TIME CMD root 1 0 0 Dec27 ? 00:00:00 /bin/bash /bootstrap.sh root 7 1 0 Dec27 ? 00:00:00 /usr/sbin/dovecot -F -c
2017 Jul 10
0
[Gluster-devel] gfid and volume-id extended attributes lost
@ pranith , yes . we can get the pid on all removexattr call and also print the backtrace of the glusterfsd process when trigerring removing xattr. I will write the script and reply back. On Sat, Jul 8, 2017 at 7:06 AM, Pranith Kumar Karampuri <pkarampu at redhat.com > wrote: > Ram, > As per the code, self-heal was the only candidate which *can* do > it. Could you check
2019 Dec 30
0
Issue running Dovecot in Docker Container
If you are running your container as root. You will not have the issues I encountered. Dovecot is dropping to the 'dovecot' and 'dovenull'(?) when needed, this is fine. PS. I would not recommend using internal logging, use something like this to log to the host or remote syslog. docker run -v /dev/log:/dev/log -it dovecot-proxy -----Original Message----- Subject: Re: Issue
2019 Dec 30
0
Issue running Dovecot in Docker Container
I'm not using internal logging. I'm running the docker with the logging to the host. I have used the same options you have specified. The problem is that the below processes are not running inside docker container whereas the standalone dovecot is running these processes(meaning without container) dovecot-Dovecot/auth dovecot-Dovecot/ssl-params dovecot-Director/lmtp
2017 Sep 23
2
Potential infinite loop in MemorySSAUpdater
With regards Bhargav Reddy Godala Software Engineer 2 Bangalore, India E-mail: Bhargav-reddy.Godala at amd.com<mailto:Bhargav-reddy.Godala at amd.com> Ext 30678 On 23-Sep-2017, at 9:27 PM, Daniel Berlin <dberlin at dberlin.org<mailto:dberlin at dberlin.org>> wrote: On Sat, Sep 23, 2017 at 8:38 AM, Godala, Bhargav-reddy via llvm-dev <llvm-dev at
2017 Jul 10
0
[Gluster-devel] gfid and volume-id extended attributes lost
Ram, If you see it again, you can use this. I am going to send out a patch for the code path which can lead to removal of gfid/volume-id tomorrow. On Mon, Jul 10, 2017 at 5:19 PM, Sanoj Unnikrishnan <sunnikri at redhat.com> wrote: > Please use the systemtap script(https://paste.fedoraproject.org/paste/ > EGDa0ErwX0LV3y-gBYpfNA) to check which process is invoking remove xattr
2003 Nov 12
1
(HI,new to asterisk)connecting asterisk to telephonyhardware
Hi, i have configured asterisk to SIP soft phones. Iam confused about the telephony interfaces like T1,E1,PRI interfaces and how to cnfigure them to asterisk. If iam using a dialogic card in the asterisk server .Can i use this card with a telephone line to dialout to different numebr in the telecom network. SIP-softphone------->---asterisk------>Dialogic card--->telephone line
2017 Jul 08
2
[Gluster-devel] gfid and volume-id extended attributes lost
Ram, As per the code, self-heal was the only candidate which *can* do it. Could you check logs of self-heal daemon and the mount to check if there are any metadata heals on root? +Sanoj Sanoj, Is there any systemtap script we can use to detect which process is removing these xattrs? On Sat, Jul 8, 2017 at 2:58 AM, Ankireddypalle Reddy <areddy at commvault.com> wrote: >
2017 Jul 10
2
[Gluster-devel] gfid and volume-id extended attributes lost
Thanks for the swift turn around. Will try this out and let you know. Thanks and Regards, Ram From: Pranith Kumar Karampuri [mailto:pkarampu at redhat.com] Sent: Monday, July 10, 2017 8:31 AM To: Sanoj Unnikrishnan Cc: Ankireddypalle Reddy; Gluster Devel (gluster-devel at gluster.org); gluster-users at gluster.org Subject: Re: [Gluster-devel] gfid and volume-id extended attributes lost Ram,
2017 Jul 07
0
[Gluster-devel] gfid and volume-id extended attributes lost
We lost the attributes on all the bricks on servers glusterfs2 and glusterfs3 again. [root at glusterfs2 Log_Files]# gluster volume info Volume Name: StoragePool Type: Distributed-Disperse Volume ID: 149e976f-4e21-451c-bf0f-f5691208531f Status: Started Number of Bricks: 20 x (2 + 1) = 60 Transport-type: tcp Bricks: Brick1: glusterfs1sds:/ws/disk1/ws_brick Brick2: glusterfs2sds:/ws/disk1/ws_brick