search for: kicked

We just built a new server to run Icecast 1.3.11 and Ices 0.22. It's a Dual PIII running RH7.1. We put it online last night and Icecast ran fine for 20 hours. Then it started throwing some errors.. That's when Ices died. Ices reported a libshout error. Part of the Icecast log is included. What can I do about this? Hunter [26/Aug/2001:16:05:01] [32:Connection Handler] Accepted

I''m trying to set up a system in which the web devs can deploy new websites via puppet kick. I''m not having a problem with puppet kick itself, but rather figuring out how to make my "webserver::sitelist" class *only* get deployed via puppet kick, and not have it regularly evaluated in the nodes.pp file. I don''t want webserver::sitelist to ever get

Hi, Is there a way of issuing a puppet kick to multiple hosts without LDAP? I see the puppet kick options suports this with "all" and "class" but only with LDAP at present. I have a number of hosts so specifying each host using it''s FQDN is a bit messy. I''ve tried using "--no-fqdn" but get: "hostname was not match with the server

Hello, Dovecot 2.2.27 (Debian Jessie backports). When issuing a "doveadm kick" for a specific user I was greeted by: --- "warning: other connections would also be kicked from following users:" --- and a list of 22odd thousand users. As it turns out, kick wants to smack the hibernation proces(ses) that have hibernated sessions for this user, obviously the wrong approach here. If there's doveadm command to wake up and thus un-hibernate sessions for a speci...

How do I stop the "you have been kicked by this conference" message from speaking? I first had MeetMe(conf, l) and I get the kicked message. I tried Meetme(CONF, lq) and I still get he kicked message. and it still says it. Thanks, Jerry

Hello, I have basically two questions regarding *puppet kick* (old puppetrun) when calling a "puppet kick host1.com host2.com host3.com" : first question) does puppet kick deploy the catalogue on the three hosts serially or in parallel?? and 2) what happens if for any reason the deployment fails on host1 ?? will puppet continuing deploying on host2 and host3 or will

Hi All, I am working on Asterisk 12.6.0 with ConfBridge module, when there are multiple user like admin and normal participant running with conference. When I try to kicked 2 user (Normal User), it play file "conf-kicked" and again join conference My scenario in confbridge like. 1] Admin User (e.g. SIP/8484-00000000) 2] Normal User (e.g. SIP/8484-00000001) 3] Admin User (e.g. SIP/8484-00000002) When I try to execute confbridge kick using below AMI. Action...

Something I noticed on a 2.1.7 director test cluster (two directors, three backends): 'doveadm proxy kick user' will kick all connections for that user on that director only. Any additional connections on other directors will remain active unless the command is run on all directors. Are the proxy and director sub-commands intended to be separate and distinct in their operation? If so,

Hi, I've just seen a new thread asking about kicking clients off the server and wondered, if there is a feature to kick sources off the server as well. This would be very useful if the server is used by multiple djs on a radio-station with a timetable. So when a dj forgets to stop his livestream the next dj could just kick the source instead of killing and restarting the whole server.

On 2018/12/6 ??6:54, Michael S. Tsirkin wrote: > When use_napi is set, let's enable BQLs. Note: some of the issues are > similar to wifi. It's worth considering whether something similar to > commit 36148c2bbfbe ("mac80211: Adjust TSQ pacing shift") might be > benefitial. I've played a similar patch several days before. The tricky part is the mode switching

On 2018/12/6 ??6:54, Michael S. Tsirkin wrote: > When use_napi is set, let's enable BQLs. Note: some of the issues are > similar to wifi. It's worth considering whether something similar to > commit 36148c2bbfbe ("mac80211: Adjust TSQ pacing shift") might be > benefitial. I've played a similar patch several days before. The tricky part is the mode switching

This patch allows virtio-blk to release its block queue lock while kicking the host. This improves scalability on SMP guests who would otherwise spin on the lock while another vCPU is kicking the host. This approach can be used for other virtio devices too. It simply splits the virtqueue_kick() operation into a prepare step which requires that the lock be held and the actual notify step which

This patch allows virtio-blk to release its block queue lock while kicking the host. This improves scalability on SMP guests who would otherwise spin on the lock while another vCPU is kicking the host. This approach can be used for other virtio devices too. It simply splits the virtqueue_kick() operation into a prepare step which requires that the lock be held and the actual notify step which

Holding the vblk->lock across kick causes poor scalability in SMP guests. If one CPU is doing virtqueue kick and another CPU touches the vblk->lock it will have to spin until virtqueue kick completes. This patch reduces system% CPU utilization in SMP guests that are running multithreaded I/O-bound workloads. The improvements are small but show as iops and SMP are increased. Khoa Huynh

Holding the vblk->lock across kick causes poor scalability in SMP guests. If one CPU is doing virtqueue kick and another CPU touches the vblk->lock it will have to spin until virtqueue kick completes. This patch reduces system% CPU utilization in SMP guests that are running multithreaded I/O-bound workloads. The improvements are small but show as iops and SMP are increased. Khoa Huynh

A channel may still be processed by the PBDMA even after removal, unless it is properly kicked. Some chips are more sensible to this than others, with GM20B triggering the issue very easily (the PBDMA will try to fetch methods from the previously-removed channel after a new one is added). Make sure this cannot happen by kicking the channel right after it is disabled, and before the new runl...

We would like to avoid pre-scheduled updates in our production environment by puppet. The solution I''ve come across is to instruct the puppet agent not to update on a schedule and instead use "puppet kick" from the puppet master to force updates when we''re ready to deploy them. I can''t seem to get this to work. I have asked around the IRC channel and

Right now we emit on every kick, but this is only necessary if something will ever be able to observe that the fence completed. If there are no refs, leave the fence alone and emit it another day. This also happens to work around an issue for the kick handler -- a kick can be a result of e.g. nouveau_bo_wait or explicit kick, or it can be due to lack of space in the pushbuf. We want the emit to

Hi all, My scenario is such that I have three users connected to a conference. CLI> meetme list 1234 User #: 01 9176502096 <no name> Channel: Zap/23-1 (unmonitored)00:00:32 User #: 02 john john Channel: SIP/john-b7800468 (unmonitored) 00:00:28 User #: 03 6463875998 <no name> Channel: Zap/22-1 (unmonitored)00:00:19 3 users in that

virtio spec requires that all drivers set DRIVER_OK before using devices. While rpmsg isn't yet included in the virtio 1 spec, previous spec versions also required this. virtio rpmsg violates this rule: is calls kick before setting DRIVER_OK. The fix isn't trivial since simply calling virtio_device_ready earlier would mean we might get an interrupt in parallel with adding buffers.