similar to: my icecast problem

Quick question? Is there a way to observe the TCP/IP block numbers produced by a client connected to a server that is not getting data fast enough or too fast in icecast while it happens in real time? I suppose you might be able to do this with a sniffer of some sort but I am just wondering about the accuracy of the results. Having access to this information in real time would help with trouble

I've managed to get some more debug info in the logs. I cleared the log, changed the log debug level to 4 and started icecast, shout and a client. Here are some relevant lines from the log : CLIENT CONNECTION : [01/Mar/2001:11:36:58] [6:Connection Handler] Accepted client 2 from ... This client connection ends up as source thread 5. The first error is mentioned after about 20 minutes.

On Wed, 28 Feb 2001, Kelly Lee Myers wrote: > In addition is there a way to set the size of the outgoing packets or is > that completely handled by the stack and not icecast itself. Forgive me if > that sounds stupid, but I didn't really get that deep into icecast > configuration. You can... but... Someone correct me if I'm wrong, but you want to look at the MTU for your

It is going to depend on a number of factors. Linux sets (along with a few other OS's I'm sure) its MTU to 1500. The problem is, if you set it longer then it will most likely be frag'd by your router. If that router does not, then another will. I think MTU for ppp interfaces are smaller. Likewise, if your backbone is FDDI, it has a large frame (somewhere in the 8000 range I

You're going to need root access. Presumably you have it if you have control over icecast. You could do a simple adduser. Then use your favorite editor and open up the /etc/passwd file (again as root). You'll need to read up on what each of the fields are, but in short you'll want to * the password field for that new user. You'll also want to change the shell to /bin/false.

> I don't know about the rest of you, but I'm not charging anything. As > mentioned, the royalties to record labels still stand if you don't follow > the rules, but this will be true regardless of the format > (mp3/vorbis/whatever.) Do you have any ads on your site? That's probably streaming related revenue. Do you list on shoutcast.com? There's definately

On Wed, 4 Apr 2001, John Griffiths wrote: > i've set up an old 486 running debian 2.2r2 using the debian icecast packages (shout doing the streaming). As my sig points out, yes, it is possible. RiR is linux and icecast stripped to the bare necessities. > so far so good, with a bit of fiddling i had a stream that worked fine over the local network As I too have seen in practice :/

REMOVE yourself for mthe list!!!!!!!!!!!! Hint: what text is repeated twice in the following message (three times if you got it from the mailing list)? PS the filtering is apparently not working. (and neither is the ignoring). :) On Sunday, 25 February 2001 at 18:46, Albi Rebmann wrote: > > To unsubscribe from this list, send a message to 'icecast-request@xiph.org' > >

In article <983130226.25873@phzzzt.atww.org> you wrote: : 1) With regards to the recent buffer-overflow exploit and the : recommendation of running icecast as a non-root user, how exactly does : one do that? I do it via "su". I use a pseudo user named "ice" and have this in a shell program that starts icecast: exec su --login -c

> > Hmm. I tried a windows laptop box (kinda slow) and indeed after about > > 30-40 minutes playback starts stuttering and eventually disconnects > > from the icecast server. > > > > Nothing else is running on this box. What gives? Why am I losing about > > 25% of the connections to this error? > > Are you using shout? Let me clarify here with the

Hi, I'm having a problem accessing my samba server from Windows. The problem occurs every time I try to browse to it on either XP or 2003 Server. The error message I get is: "\\Zeus is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The account is not authorized to log in

I'm trying to use zfs acls in solaris 10. I've looked at past posts regarding this and some online help, but am stuck. I'm currently using samba 3.3.9; I've had the same problem with 3.3.7. samba is compiled and running as an Active Directory member server (compiled with ldap and kerberos). The zfs disk is local. I'm not using winbind. I compiled with zfsacl module.

Hi, Our samba server is running Red Hat Enterprise Linux ES release 4 (Nahant Update 4) with samba version: samba-3.0.33-0.17.el4. We like to authenticate all the users with our Primary Domain Controller wnidows 2008. Some users keep getting asked to enter username and password. Even with the correct password, still can't access the drive. The strange thing is that some users are

Hello, We use samba to backup some (rather large) sql databases. Lately we ocasionally are getting fail reports, as in the file could not be written, and windows generating an error 64: "The specified network name is no longer available" While going trough the logs, i can see the following error (sorry for the long output): ----- [2008/05/19 01:14:46, 0]

I'm doing some testing with Win7 RC1 and I'm having an identical problem with two CentOS servers (5.2 and 5.3) both running Samba 3.0.33 where I cannot authenticate. Both servers are authenticating with Winbind to an AD DC. I have a third CentOS 5.2 server with Samba 3.0.33 shares that does not use Winbind which has no problems. This pops up in smbd.log: (.200 is wireless and .184 is my

hi all, i have a Samba version 3.2.5 server running in a debian 5.0.8 (a little old, i know...). the network setup is: -one local office using samba -one remote office (we call it cberg) using samba remotely over a vpn (linksys-cisco) -another remote office (we call it colon) using samba remotely over a vpn (linksys-cisco) the local office and colon office are working fine the remote office

Hello, I'm running samba-3.0.33 (samba-3.0.33-3.15.el5_4) On Centos 5.4 and some files have issues being copied from the Samba server to the Vista (Service Pack 1) clients local disk via Windows Explorer, copying too the Samba server also has no issues and copying via the CMD prompt has no problem, I'm getting the following errors 1. Invalid MS-DOS Function

Hello mailing-list, this is my first post and i hope that you enjoy my very bad but sometimes funny english. My Problem is the following: First of all, my server-config: Samba Version 3.0.20b-3.4-SUSE on a SUSE Linux Enterprise Server 9 with Kernel 2.6.5-7.252-smp Now the problem is, that samba generally works fine, but it doesn't work to work with a special application directly on a

I'm having problems connecting from my laptop, and the logs show lib/util_sock.c:send_smb(769) Error writing 116 bytes to client. -1. (Broken pipe) : 1 Time(s) lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.0.91. Error Broken pipe : 1 Time(s) libsmb/smb_signing.c:srv_check_incoming_message(737) srv_check_incoming_message: BAD SIG: seq 2 wanted

I've been fighting with a samba install on top of a amd64 Ubuntu 10.4 system for a couple months now. I have a small flotilla of Windows systems running anything from Win 2000 up through Windows Server 2008. All save for the 2008 systems are setup with nightly NTBackup jobs with my samba server as the destination. The 2008 systems are running MS SQL and use the samba server as the