Displaying 20 results from an estimated 3000 matches similar to: "sir please let me know ( Installation problem)"
2005 Dec 25
4
Use of TCP_CORK instead of TCP_NODELAY
We're abusing icecast in a true narrowcasting setup (personalized stream per
mountpoint). The streams itself are created in a piece of proprietory
(spelling?, i'm dutch) software, icecast merely relays them.
However, the intended endpoint is an embedded device. This device has
trouble with tcp/ip packets not matching the max. packet size (MSS or MSS
minus header). After eleborate testing,
2005 Dec 28
2
Use of TCP_CORK instead of TCP_NODELAY
>
> p.s. For an in depth analysis of TCP_CORK read Christiopher Baus' excelent
> article: http://www.baus.net/on-tcp_cork
Thanks for this pointer. I'd been meaning to reply on this thread, but
hadn't got around to it, primarily because I didn't really understand
TCP_CORK (the linux manpage is, as usual, fairly unclear on what
exactly it does). Now I understand!
>
>
2005 Dec 28
0
Use of TCP_CORK instead of TCP_NODELAY
Hi Henri and others,
Very interesting post about TCP_CORK. I would be very interested in having
it applied in the next version of Icecast.
I'm using Icecast in a somewhat narrowcasting setup with large numbers of
sources (> 100) and between 5 and 50 listeners per source. All streaming is
done at low bitrates (16 - 24 kbit/sec) and listeners use embedded devices
connected by 56k modems. It
2005 Dec 28
0
Use of TCP_CORK instead of TCP_NODELAY
Michael,
With regard to your comment below:
> As a streaming server, it's fairly crucial for icecast to send out
> data with as low a delay as possible (many clients don't care, but
> some do). That's why we use TCP_NODELAY - we actually WANT to send out
> data as soon as we can.
Can you explain how some clients depend on a low delay when receiving data
from icecast? How
2005 Oct 05
3
icecast2 mountpoints maximum
We are using icecast as stream-relay for a true narrowcast solution
we've developed. The idea behind the system is that each individual
client gets it's own mountpoint.
Basically we have an application that creates streams. Its written in
c++ and uses libshout to handle connecting to icecast.
Everything works fine, as long as we keep the number of mountpoints
below 347. As soon as we
2010 Oct 10
3
pop3 TCP_CORK too late error
I was straceing a pop3 process and noticed that the TCP_CORK option
isn't set soon enough:
epoll_wait(8, {{EPOLLOUT, {u32=37481984, u64=37481984}}}, 38, 207) = 1
write(41, "iTxPBrNlaNFao+yQzLhuO4/+tQ5cuiKSe"..., 224) = 224
epoll_ctl(8, EPOLL_CTL_MOD, 41, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP,
{u32=37481984, u64=37481984}}) = 0
pread(19,
2005 Dec 28
2
Use of TCP_CORK instead of TCP_NODELAY
Klaas Jan Wierenga wrote:
> Hi Henri and others,
>
> Very interesting post about TCP_CORK. I would be very interested in having
> it applied in the next version of Icecast.
I'd be more interested in some figures to show there being a benefit,
most examples talk about HTTP servers with short lived connections where
sendfile(2) is used.
> For low-bitrate streams the problem
2016 Apr 12
2
Slow reading of large dovecot-uidlist files
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 12 Apr 2016, Bostjan Skufca wrote:
> On 12 April 2016 at 10:23, A.L.E.C <alec at alec.pl> wrote:
>
>> I don't know dovecot's code, but I suppose it uses uidlist file to get
>> mailbox statistics that it returns as EXISTS, RECENT, UNSEEN, UIDNEXT,
>> UIDVALIDITY, etc, which are required by IMAP standard. I
2019 Jun 06
4
[nbdkit PATCH 0/2] Reduce network overhead with corking
Slightly RFC, as I need more time to investigate why Unix sockets
appeared to degrade with this patch. But as TCP sockets (over loopback
to localhost) and TLS sessions (regardless of underlying Unix or TCP)
both showed improvements, this looks like a worthwhile series.
Eric Blake (2):
server: Add support for corking
server: Cork around grouped transmission send()s
server/internal.h | 3
2019 Mar 08
1
Dovecot v2.3.5 released
On 7.3.2019 23.37, A. Schulze via dovecot wrote:
>
> Am 07.03.19 um 17:33 schrieb Aki Tuomi via dovecot:
>
>>> test-http-client-errors.c:2989: Assert failed: FALSE
>>> connection timed out ................................................. : FAILED
> Hello Aki,
>
>> Are you running with valgrind or on really slow system?
> I'm not aware my buildsystem
2010 Mar 09
2
rcom package
Hi,
I would like to make a program that reads excel files, and writes the cells of which contents is not a formula to another file. I don't think this is possible with RODBC, but it may be possible with rcom.
I read the documentation of the rcom package, but I was hoping somebody knows a good web resource for more eleborate info. I tried Googling, but alas (did you know rcom also is a
2009 Sep 07
4
Upgrade from b113 to b122 - any gotchas
We are running 4 Solaris10u7 DomUs on a b113 Dom0
I''d like to upgrade the Dom0 to b122 but not rebuild the DomUs. Below
is a typical DomU xml dump. Is there anything obvious that will bite
me in upgrading from 113 to 122?
Thanks
John
virsh # dumpxml achilles2
<domain type=''xen'' id=''1''>
<name>achilles2</name>
2005 Oct 12
3
Icecast logging
Hi Guys,
My first post here so hello to all :-))
Anyway, my question: Does anybody know if there is a tool out there that can
process the icecast log files and return a graph of listener numbers over a
set period?
I'd like to be able to know when our most busiest time was.
Thanks very much in advance,
Andy
2005 Sep 13
1
Solaris build failed
dovecot-v1.0-alpha build failed for Solaris 11 (OpenSolaris Nevada).
The problematic line is in socket.c line 228. The fix should be to
change SOL_TCP to IPPROTO_TCP found in netinet/in.h. This change should
work universally on all platforms.
Gary
2005 Dec 28
0
Use of TCP_CORK instead of TCP_NODELAY
> As a streaming server, it's fairly crucial for icecast to
> send out data with as low a delay as possible (many clients
> don't care, but some do). That's why we use TCP_NODELAY - we
> actually WANT to send out data as soon as we can.
Nagle is inherently unsuited for streams. NODELAY was (imho) ment for
connections for which Nagle isn't sufficient and CORK is not
2005 Dec 29
1
Use of TCP_CORK instead of TCP_NODELAY
Klaas Jan Wierenga wrote:
>>This is exactly why it was implemented, a few people complained about
>>the overhead with large numbers of listeners, not only because of the
>>TCP overhead but also the fact that it reduces the write syscall
>>overhead. Will TCP_CORK (linux) and TCP_NOPUSH (BSD) give noticable
>>benefits wrt icecast? It might prove helpful if available but
2007 Nov 28
1
Cross-compiling asterisk-1.4 for Debian on a slug
Hi folks!
I planned to put asterisk-1.4 on my slug (one of these embedded devices).
Since i don't want to compile it natively on this slow processor, i need
a cross-compile toolchain. I tried out several ways such as manually
compiling binutils and gcc, or using scratchbox. All of these with the
result that i got binaries for machines except the one i wanted! :(
I then have been given a link
2013 May 27
1
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
[root at localhost IceCast]# cd libvorbis
[root at localhost libvorbis]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets $(MAKE)... yes
checking for working aclocal-1.4... missing
checking for working autoconf... missing
checking for working automake-1.4... missing
checking for working
2014 Jun 24
2
Crash in service imap with version 2.2.13
Hi,
yesterday I upgraded to version 2.2.13 under Debian Squeeze.
Since today morning sometimes my logfile shows the folling error:
..
Jun 24 10:14:16 mailstore dovecot: imap(user at domain.net pid:23434 session:<jf6yi5D8TADD/vzh>): Fatal: master: service(imap): child 23434 killed with
signal 11 (core dumped)
...
The kernel error log shows:
...
Jun 24 10:14:16 mailstore kernel:
2017 Jan 31
3
quota-status returns quota_status_success when email would put user over quota
Am 31. J?nner 2017 16:36:35 MEZ schrieb Kristian Pedersen <kp at asom-net.dk>:
>Hi list,
>
>We still did not manage to get quota-status working.
>We're hoping someone can provide some feedback/ideas on how we may
>investigate this issue further?
>Is it likely to be a bug fixed in a newer version?
>
>Regards,
>
>Kristian
>
>
[...]
>>
>>