search for: memlock

...un DNS. (It will not, however, install the program nor train it.) I set up real-time audio access as follows: sudo su -c 'echo @audio - rtprio 99 >> /etc/security/limits.conf' sudo su -c 'echo @audio - nice -20 >> /etc/security/limits.conf' sudo su -c 'echo @audio - memlock 1500000 >> /etc/security/limits.conf' So as I understand it, rtprio is the correct #, nice is the lowest possible, and I memlocked half my RAM. In winecfg, I have audio set to 48000 default sample rate. I have an internal hda-intel soundcard (bad but better since alsa upgraded to 1.0...

...Instruments Kontakt 4 under Wine. It runs fine except for occasional stutters, so I wanted to try enabling Realtime in Jack, but I have no luck with this. (I have made recommended edits to the limits.conf file, though I've read that this is no longer necessary(?): @audio - rtprio 100, @audio - memlock 250000) When I start up Kontakt, I see "ASIO_Kontakt 4" appear in the Jack Connections "Readable Clients/Output Ports" window in the Audio tab, which is normal. However, it quickly disappears, and when Kontact boots fully, no sound libraries can be loaded and the program locks...

...hed starting up and ready to > serve connections > [2018/02/15 10:39:03.009569, 2] ../source3/smbd/server.c:1395( > smbd_parent_loop) > waiting for connections > > Here are my settings in /etc/security/limits. > > * soft nofile 99000 > * hard nofile 999000 > * - memlock unlimited > * - nofile 100000 > * - nproc 32768 > * - as unlimited > > @root soft nofile 99000 > @root hard nofile 999000 > @root - memlock unlimited > @root - nofile 100000 > @root - nproc 32768 > @root - as unlimited > > > Again thanks for you help, >...

...lient-rpc-fops.c:2578:client3_3_readdirp_cbk] 0-glurch-client-3: remote operation failed [Transport endpoint is not connected] [2018-05-20 20:38:27.733181] W [fuse-bridge.c:2897:fuse_readdirp_cbk] 0-glusterfs-fuse: 72882828: READDIRP => -1 (Transport endpoint is not connected) I already set the memlock limit for glusterd to unlimited, but the problem persists. Only going from RDMA transport to TCP transport solved the problem. (I'm running the volume now in mixed mode, config.transport=tcp,rdma). Mounting with transport=rdma shows this error, mouting with transport=tcp is fine. however,...

RID solved my problem. But while reading docs I saw new things and I changed my smb.conf completely. I have read almost every parameter but i'm still not %100 sure. Can you do me a last favor? Please can you tell me do I have any problem with new smb.conf? Kernel: Linux 4.14.13-1-ARCH Filesystem: zfs-linux 0.7.5.4.14.13.1-1 Thank you so much for your help. --------------------- [global]

We were previously running 5.1 x86_64 and recently updated to 5.2 using yum. Under 5.1 we were having problems when running jobs using torque and the solution had been to add the following items to the files noted "* soft memlock unlimited" in /etc/security/limits.conf "session required pam_limits.so" in /etc/pam.d/{rsh,sshd} This changed the max locked memory setting in ulimit as follows: Before the change rsh nodeX ulimit -a still gives us max locked memory (kbytes, -l) 32 After the...

...nnections > > [2018/02/15 10:39:03.009569, 2] ../source3/smbd/server.c:1395( > > smbd_parent_loop) > > waiting for connections > > > > Here are my settings in /etc/security/limits. > > > > * soft nofile 99000 > > * hard nofile 999000 > > * - memlock unlimited > > * - nofile 100000 > > * - nproc 32768 > > * - as unlimited > > > > @root soft nofile 99000 > > @root hard nofile 999000 > > @root - memlock unlimited > > @root - nofile 100000 > > @root - nproc 32768 > > @root - as unlimited...

...addirp_cbk] > 0-glurch-client-3: remote operation failed [Transport endpoint is not > connected] > [2018-05-20 20:38:27.733181] W [fuse-bridge.c:2897:fuse_readdirp_cbk] > 0-glusterfs-fuse: 72882828: READDIRP => -1 (Transport endpoint is not > connected) > > I already set the memlock limit for glusterd to unlimited, but the problem > persists. > > Only going from RDMA transport to TCP transport solved the problem. (I'm > running the volume now in mixed mode, config.transport=tcp,rdma). Mounting > with transport=rdma shows this error, mouting with transport=...

...h-client-3: >> remote operation failed [Transport endpoint is not connected] >> [2018-05-20 20:38:27.733181] W [fuse-bridge.c:2897:fuse_readdirp_cbk] >> 0-glusterfs-fuse: 72882828: READDIRP => -1 (Transport endpoint is not >> connected) >> >> I already set the memlock limit for glusterd to unlimited, but the >> problem persists. >> >> Only going from RDMA transport to TCP transport solved the problem. (I'm >> running the volume now in mixed mode, config.transport=tcp,rdma). Mounting >> with transport=rdma shows this error, mou...

...; unprivileged pod, with some host mounts / capabilities added to the > > pod, needed by libvirtd and other services. > > > > One of the capabilities libvirtd requires for successful startup > > inside a pod is SYS_RESOURCE. This capability is used to adjust > > RLIMIT_MEMLOCK ulimit value depending on devices attached to the > > managed guest, both on startup and during hotplug. AFAIU the need to > > lock the memory is to avoid pages being pushed out from RAM into swap. > > Libvirt shouldn't set RLIMIT_MEMLOCK by default, unless there's > so...

...isk cache. I did some research and this looks like a > bad design from the Kernel people. Meanwhile all you can do us every 60 > seconds: echo 3 | sudo tee /proc/sys/vm/drop_caches Asterisk should be able to reserve memory and force it to stay locked in memory, exactly like Mariadb does with memlock=1 Would the Asterisk developers consider something like this? > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200926/a3a7fb71/attachment.html>

...nd this looks like a >> bad design from the Kernel people. Meanwhile all you can do us every 60 >> seconds: > > echo 3 | sudo tee /proc/sys/vm/drop_caches > Asterisk should be able to reserve memory and force it to stay locked in > memory, exactly like Mariadb does with > memlock=1 > Would the Asterisk developers consider something like this? > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200926/19143ad9/attachment.html>

thomas.ruecker wrote: > > Hi, > > Try replacing $USER with your exact username. (the one printed at the > command prompt in the terminal) > > Cheers > > Thomas > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > OK, it worked, I added myself to the

...s / capabilities added to the > >>> pod, needed by libvirtd and other services. > >>> > >>> One of the capabilities libvirtd requires for successful startup > >>> inside a pod is SYS_RESOURCE. This capability is used to adjust > >>> RLIMIT_MEMLOCK ulimit value depending on devices attached to the > >>> managed guest, both on startup and during hotplug. AFAIU the need to > >>> lock the memory is to avoid pages being pushed out from RAM into swap. > > > I recall successfully testing GPU assignment from an unpri...

...c:2578:client3_3_readdirp_cbk] 0-glurch-client-3: remote operation failed [Transport endpoint is not connected] > [2018-05-20 20:38:27.733181] W [fuse-bridge.c:2897:fuse_readdirp_cbk] 0-glusterfs-fuse: 72882828: READDIRP => -1 (Transport endpoint is not connected) > > I already set the memlock limit for glusterd to unlimited, but the problem persists. > > Only going from RDMA transport to TCP transport solved the problem. (I'm running the volume now in mixed mode, config.transport=tcp,rdma). Mounting with transport=rdma shows this error, mouting with transport=tcp is fine....

...pod, with some host mounts / capabilities added to the >>> pod, needed by libvirtd and other services. >>> >>> One of the capabilities libvirtd requires for successful startup >>> inside a pod is SYS_RESOURCE. This capability is used to adjust >>> RLIMIT_MEMLOCK ulimit value depending on devices attached to the >>> managed guest, both on startup and during hotplug. AFAIU the need to >>> lock the memory is to avoid pages being pushed out from RAM into swap. I recall successfully testing GPU assignment from an unprivileged libvirtd sever...

...e_timeout=172800 default-storage-engine = INNODB default-character-set = utf8 max_connections = 500 max_connect_errors=100000 max_allowed_packet = 4M max_heap_table_size = 1024M max_length_for_sort_data = 4096 net_buffer_length = 8K sort_buffer_size = 8M join_buffer_size = 16M #if lock memory #memlock table_cache = 1024 thread_cache_size = 512 thread_concurrency = 8 query_cache_type=0 #memory table max size tmp_table_size = 128M #******************************* Logs related settings *************************** log-error=/usr/local/mysql/log/error3.log long_query_time = 1 log_long_format slo...

...urces. In this case, libvirtd is running inside an unprivileged pod, with some host mounts / capabilities added to the pod, needed by libvirtd and other services. One of the capabilities libvirtd requires for successful startup inside a pod is SYS_RESOURCE. This capability is used to adjust RLIMIT_MEMLOCK ulimit value depending on devices attached to the managed guest, both on startup and during hotplug. AFAIU the need to lock the memory is to avoid pages being pushed out from RAM into swap. In KubeVirt world, several libvirtd assumptions do not apply: 1. In Kubernetes environments, swap is usuall...

...gt;>>> pod, needed by libvirtd and other services. > >>>>> > >>>>> One of the capabilities libvirtd requires for successful startup > >>>>> inside a pod is SYS_RESOURCE. This capability is used to adjust > >>>>> RLIMIT_MEMLOCK ulimit value depending on devices attached to the > >>>>> managed guest, both on startup and during hotplug. AFAIU the need to > >>>>> lock the memory is to avoid pages being pushed out from RAM into > swap. > >> > >> > >> I recall s...

...s added to the >>>>> pod, needed by libvirtd and other services. >>>>> >>>>> One of the capabilities libvirtd requires for successful startup >>>>> inside a pod is SYS_RESOURCE. This capability is used to adjust >>>>> RLIMIT_MEMLOCK ulimit value depending on devices attached to the >>>>> managed guest, both on startup and during hotplug. AFAIU the need to >>>>> lock the memory is to avoid pages being pushed out from RAM into swap. >> >> >> I recall successfully testing GPU assign...