similar to: No Duplicate Users - Patch

On Monday 17 May 2004 01:23, oddsock wrote: > I'd like to commit the following patch which adds a new option to the > htpasswd client authenticator. This option <option > name="allow_duplicate_users"> specifies wether or not the same username can > connect to a mountpoint more than once. This is pretty much a required > feature for any decent use of the

Hello, after the reply of Jerome Alet, I forward our questions to you. I hope it is now the right place to put it. Could you please send your answers, questions, comments to interopcast-general@nongnu.org so everyone in the group can get a copy of it. Thank you. ----- Original Message ----- From: "Jerome Alet" <alet@librelogiciel.com> To: <interopcast-general@nongnu.org>

Thank you for your time...we made some changes to our config file and the server doesn't want to start with the command icecast -c /path/to/icecast.xml giving the error: 'Could not create listener socket on port 8000 Server startup failed. Exiting' can you look at the config file bellow and let us know of any changes that might help. we need to be able to have 10,000 clients

Hi All. Attached is a patch against OpenBSD, based in part on the owl-always-auth patch. The idea is that the only way out of auth_passwd for the failure case is the "return 0" at the bottom. I don't know if this is a good way to do it or not, it's presented for discussion. Also, I don't think 3.6.1p2 is quite right WRT these timing issues (eg, you get a fast failure

Windows authentication extends far beyond the CIFS protocol the Samba implements, but it only very recently that work has been done to catch up to Microsoft's extensions in this area. This has caused many administrators pain and toil that their MS counterparts simply don't have. For them, authentication 'just works', with single-sign-on and the lot. I have worked, for over a

Attached you will find a patch against the icecast-2.0.0 released source code which implements listener time limits on a global or mount-specific scope. Two new configuration elements are added with this patch: client-time-limit: This is a GLOBAL directive which covers all connections. Its value is given in seconds. So for example, if you want to limit all listeners on all mount points to 1

<mount> <on-connect>/home/icecast/bin/source-start</on-connect> <on-disconnect>/home/icecast/bin/source-end</on-disconnect> </mount> --- Phil / w2lie http://www.w2lie.net On 2013-07-24 12:33, Miguel s wrote: > anyone knows if is possible to create an email alert to notify me when a mount point is connecting and disconnecting? > >

At 10:26 AM 5/16/2004, you wrote: > > I'd like to commit the following patch which adds a new option to the > > htpasswd client authenticator. This option <option > > name="allow_duplicate_users"> specifies wether or not the same username > can > > connect to a mountpoint more than once. This is pretty much a required > > feature for any

Yes, I know, but, from what I see, the "allow_duplicate_users = 0" option is not really usable, because of these problems that it generates in many players. Therefore, I think it would be interesting for Icecast to allow the option to limit to 2 (or those defined in the configuration), so that it can be used and limited, at least. I think that new option is very necessary. El sáb., 14

Hi, A radio is being developped at school, and we wanted to avoid eating too much bandwidth, so we had a look at RTP. I first implemented it in icecast1 and it worked well (although we had to apply a patch to make RTP work with xmms). We are indeed saving a lot of bandwidth. I then adapted it to icecast2, here is the patch. The biggest trouble for now is the configurability. I added 3 global

On 14 Sep 2019, at 21:54, Mikel Sanz | 20 Comunicación wrote: > Yes, it is the first thing I have tried, but I have encountered this > problem. If I enable option <option name="allow_duplicate_users" > value="1"/>, it works fine. But if set to 0, to limit one connection > per > user, it does not work properly and forces you to manually enter the >

Yes, it is the first thing I have tried, but I have encountered this problem. If I enable option <option name="allow_duplicate_users" value="1"/>, it works fine. But if set to 0, to limit one connection per user, it does not work properly and forces you to manually enter the data again. It seems that there are players who make 2 requests, and being limited to 1, makes the

On Mon, 2003-12-01 at 08:28, Melanie wrote: > > diff -b -B -r -u -P --exclude-from=ignore ../icecast/src/source.c > ./src/source.c > --- ../icecast/src/source.c Fri Nov 14 17:51:59 2003 > +++ ./src/source.c Mon Dec 1 09:14:34 2003 > @@ -139,7 +192,6 @@ > #endif > > free(source->mount); > - free(source->fallback_mount); >

http://bugzilla.mindrot.org/show_bug.cgi?id=125 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #619 is|0 |1 obsolete| | ------- Additional Comments From dtucker at zip.com.au 2004-05-31 23:25 -------

Hi I have an icecast server that relay a remote stream, with a local fallback mountpoint. When I unplug the network cable (just for test), icecast falls back to the local mountpoint after a few seconds. When I re-plug, I have to wait 1or 2 minutes before moving back to the remote stream. Why is it so long ? I'm using the default parameters, with a 128 kbps stream. <icecast>

Hi, On 2003.12.01 02:57 Michael Smith wrote: > Please, send us patches. Your complex-fallbacks one is of most interest, > and > we'd definately love to see that separately from the others, but the we'd > also like to see separate patches for the other features, so that we can > review them on their own merits (and commit them if we think they're good > enough :-) I

True - in that case, another fix ist called for, but it's just as simple: diff -b -B -r -u -P --exclude-from=ignore ../icecast/src/source.c ./src/source.c--- ../icecast/src/source.c Mon Dec 1 14:49:52 2003 +++ ./src/source.c Mon Dec 1 14:50:56 2003 @@ -72,7 +72,7 @@ src->yp_public = 0; if(mountinfo != NULL) { - src->fallback_mount = mountinfo->fallback_mount;

There are many ways to set up and manage a VPN. Tinc's roots are a "friend network", where there is a group of nodes that all trust each other, and there is no central authority. It also works well in situations where all nodes are controlled by the same authority, for example when a sysadmin configures several nodes, like within a company that wants to link together several

Could you post the config you used with comments? Currently there is at least one closing comment tag without a opening tag as far as I can see, which is confusing. If that is the file you are using, maybe you accidentally commented it out? Despite that it should works, but all of the paths in the config need to be adjusted for Windows! On 29 Nov 2015, at 22:16, Steve Matzura wrote: > If this

I tried to use MySQL stored procedures from dovecot: password_query = CALL user_pass_check('%n', '%d', '%w') user_query = CALL user_info('%n', '%d') This failed with the message: User query failed: PROCEDURE imap.user_info can't return a result set in the given context The root of this problem is that mysql_real_connect() needs to be called with