search for: _seconds_

...(for example, I could check for has_paredata before checking for serailno, which saves a couple of calls and also will avoid any change in format_mp3.[ch]). <p>[*] We must rethink the hard limit, 25, in the queue size, the queue can become larger just with the faststart buffer. A limit in _seconds_ could work better. <p> -- ricardo galli GPG id C8114D34 -------------- next part -------------- A non-text attachment was scrubbed... Name: update3b.diff Type: text/x-diff Size: 10015 bytes Desc: update3b.diff Url : http://lists.xiph.org/pipermail/icecast-dev/attachments/20030119...

...this one thing. It also needs to be defaulted to off, this isn't a feature everyone should get without thinking about whether they want to use it. > > [*] We must rethink the hard limit, 25, in the queue size, the queue can > become larger just with the faststart buffer. A limit in _seconds_ could > work better. Right, I know that limit is a problem. Time-based limits are much harder, as they require deeper format knowledge than is currently done (unless you use a hack like in your faststart stuff - but I don't really like that, either. A byte-length buffer rather than time-...

...opers take a very sane and reasonable approach by declaring mod_nsec as an uint32 -- that is, both unsigned, and having a byte-fixed reasonable size. ( This is imho how tv_nsec field should have been declared! ) Furthermore, rsync 3.1.1 -- see set_file_attrs() in rsync.c -- compares only mtime _seconds_, and takes no attempt to adjust mtimes further if the "classic" .st_mtime values coincide. ( And this is why all the "Invalid argument (22)" problems disappear after we transfer .st_mtime values by an utime() call. ) Therefore, still for rsync 3.1.1 -- first, any bogus neg...

I just implemented a system using a TE411P hardware echo cancellation card. Per Digium, I setup zaptel.conf, and zapata.conf the same way as I always have. To my surprise calls out to the PSTN had a terrible echo. 1 - 2 second delay, and quite clear. The echo was so bad that I had to remove the hardware echo cancellation module from the card. We are only using the 1st span of this card right

Hi all, I''ve not been able to find an explanation of the relationship between prio and rate as they apply to the HTB technique. Hopefully someone on here will be able to help me. As I understand things, when prio values are assigned to an HTB setup, classes with a given prio value will only be serviced when there are no packets waiting in classes with a lower prio value. Now, does