search for: infomr

Hi! In upgrading from Ubuntu 10.10 to 12.04, my mail setup (dovecot using sieve and postfix) broke pretty badly. Have gotten teh imap server working, but local delivery doesn't work. - sieve gets called, but all "fileto" actions result in "failed to store into mailbox 'zzz': Mailbox doesn't exist: zzz Dovecot version is 2.0.19, configuration is: # 2.0.19:

...ltime. > > This was the link that not work about log rotation in old mailing i > found: > https://trac.xiph.org/ticket/2173 This is most likely: https://gitlab.xiph.org/xiph/icecast-server/-/issues/2173 (It has been implemented and is part of the next release.) > Thanks for the infomration about the KH version. I use it in the past > for flash/aac. > > I test 2.5 version and have a very nice interface. > It did crash once and also had some problems with https (stop after 3 > seconds after some weeks running fine) > using fallover mountpoints) Same as 2.4.4....

...about log rotation in old mailing i > > found: > > https://trac.xiph.org/ticket/2173 > > This is most likely: > https://gitlab.xiph.org/xiph/icecast-server/-/issues/2173 > > (It has been implemented and is part of the next release.) > > > > Thanks for the infomration about the KH version. I use it in the past > > for flash/aac. > > > > I test 2.5 version and have a very nice interface. > > It did crash once and also had some problems with https (stop after 3 > > seconds after some weeks running fine) > > using fallove...

...found: > > > https://trac.xiph.org/ticket/2173 > > > > This is most likely: > > https://gitlab.xiph.org/xiph/icecast-server/-/issues/2173 > > > > (It has been implemented and is part of the next release.) > > > > > > > Thanks for the infomration about the KH version. I use it in the > > > past > > > for flash/aac. > > > > > > I test 2.5 version and have a very nice interface. > > > It did crash once and also had some problems with https (stop > > > after 3 > > > seconds...

...UA2 --|------ asterisk2 -----------------------+ DB UA3 --|------ asterisk3 -----------------------+ UA4 --|------ asterisk4 -----------------------+ | All UA is located in the same area. A seperated PC is used as a centralized DB for storing a common dial plan, user account and register infomration. UA1 can make call to UA2,UA3 and UA4. UA2 can make call to UA1, UA3 but not UA4. UA3 can make call to UA4 but not UA1, UA2 UA4 failed to make call to all UA. >From the CLI and log below, asterisk shows it can't create channel. As I expect, all UA should able to find each other. Howev...

....org/ticket/2173 > > > > > > This is most likely: > > > https://gitlab.xiph.org/xiph/icecast-server/-/issues/2173 > > > > > > (It has been implemented and is part of the next release.) > > > > > > > > > > Thanks for the infomration about the KH version. I use it in the > > > > past > > > > for flash/aac. > > > > > > > > I test 2.5 version and have a very nice interface. > > > > It did crash once and also had some problems with https (stop > > > > a...

On 2020/7/16 ??3:23, Eli Cohen wrote: > Currently, get_vq_state() is used only to pass the available index value > of a vq. Extend the struct to return status on the VQ to the caller. > For now, define VQ_STATE_NOT_READY. In the future it will be extended to > include other infomration. > > Modify current vdpa driver to update this field. > > Reviewed-by: Parav Pandit <parav at mellanox.com> > Signed-off-by: Eli Cohen <eli at mellanox.com> What's the difference between this and get_vq_ready()? Thanks > --- > drivers/vdpa/ifcvf/ifcv...

..., Eli Cohen wrote: >>> Currently, get_vq_state() is used only to pass the available index value >>> of a vq. Extend the struct to return status on the VQ to the caller. >>> For now, define VQ_STATE_NOT_READY. In the future it will be extended to >>> include other infomration. >>> >>> Modify current vdpa driver to update this field. >>> >>> Reviewed-by: Parav Pandit<parav at mellanox.com> >>> Signed-off-by: Eli Cohen<eli at mellanox.com> >> What's the difference between this and get_vq_ready()? >...

...gt;> Currently, get_vq_state() is used only to pass the available index value >>>>> of a vq. Extend the struct to return status on the VQ to the caller. >>>>> For now, define VQ_STATE_NOT_READY. In the future it will be extended to >>>>> include other infomration. >>>>> >>>>> Modify current vdpa driver to update this field. >>>>> >>>>> Reviewed-by: Parav Pandit<parav at mellanox.com> >>>>> Signed-off-by: Eli Cohen<eli at mellanox.com> >>>> What's the...

...first broke I thought thats actually a very good idea to have implemented, though it sounds the way Trixbox implemented it may have been unsecure. Maybe someone else can come up with a better way of implementing this. If the data was all randomised there's no harm in doing this; some basic infomration like; Hours of uptime Reboots Number of extensions Number of calls Number of minutes Make it totally voluntary and this would be a good thing to Digium for them to be able to be more aware of whats happening out there...apart from users downloaded the application 20 kazillion times this year....

Per the suggestion of this list when I posted on the r-help list, I have gone to cran, linux downloads and read the read me file to try and install the binary for R 2.15.1 on my ubuntu AMD64 machine. I added to my sources.list the deb http:\\cran.wustl.edu\bin\linux\ubuntu precise main . Then I ran sudo apt-get update and sudo apt-get install r-base. The system promptly installs R 2.14.1 . I

Howdy, The string of notices on BugTraq about RSAref being vulnerable to overflows has me concerned. After trying to sort through all the messages, I can't figure out whether I need to update OpenSSL (a check of their website indicates no new patches), OpenSSH, both, or neither. I am aware there is no known exploit for it yet. I could be a bad boy and just run all

We have extended collectd virt plugin to extract info about disk usage from a libvirt domain using libguestfs. In addition to my previous mail I am attaching some more infomration about the problem. Currently the collectd plugin works fine and retrieves the required statistics. The problem that I face happens after certain number of cycles (getting disk usage statistics). Collectd is terminated with the following error: Feb 20 15:09:36 tve50 collectd[17720]: *** buffer...

...avoid this problem or make it less critical. A vcpu might set a flag "no_desched" in its vcpu_info structure (I''ve used an unused hole) which will tell the xen scheduler to keep the vcpu running for some more time. If the vcpu would have been descheduled otherwise, the guest is infomred by another flag in the vcpu_info to voluntarily give up control after leaving the critical section. If the guest is not cooperative it will be descheduled after 1 msec anyway. I''ve made some tests in Dom0 with a small benchmark producing high system load using time -p (dd if=/dev/urand...

I'd love to hear more details. Are you saying that this infinite loop is a limitation of EHABI table format, and not something that can be fixed in the compiler? Meanwhile, please notice that gcc behavior matches current clang behavior that I described above. We would not want to create an incompatibility. On Fri, Feb 14, 2014 at 8:42 PM, Logan Chien <tzuhsiang.chien at gmail.com>

...t tagged with no-unwind, then it is may-unwind. * The ehtable attribute guarantees that the exception handling table, such as the LSDA handler data and (by implementation) the stack unwinding information for exception, will be generated for exception handling. If the table includes stack unwinding infomration, then it is guaranteed that the unwinding information is sufficient enough to go back to previous propagation barrier (landingpad, cleanup filter, or can't unwind.) * The uwtable attribute guarantees that the unwind table will be generated for stack unwinding for profilers, debuggers, (po...

With today''s build, my domain 0 crashes during boot when it tries to bring eth0 up (it''s an E100). cb->prev (eax) is NULL in e100_exec_cb() (e100.c:827). Just from code inspection, I don''t see how this can be. e100_alloc_cbs() was just called, which looks like it should have correctly linked up all the cb->prev/cb->next pointers. It happens regardless of

Changes since v9: * series re-ordering so make functionality more distinct. Basic vlan filtering is patches 1-4. Support for PVID/untagged vlans is patches 5 and 6. VLAN support for FDB/MDB is patches 7-11. Patch 12 is still additional egress policy. * Slight simplification to code that extracts the VID from skb. Since we now depend on the vlan module, at the time of input skb_tci is