search for: sigqueue

...The solution seems to me not broad > enough for injecting upstream. This works nice for a single device / UPS > setup, but would not make it when there are more devices, as I get it. True, I use SIGUSR1 and SIGUSR2 which do not allow a payload such as a UPS unit name. That would require SIGQUEUE, which accepts integers and pointers to other values (such as UPS unit names), but a Bash script can only send integers with SIGQUEUE. Sending pointers to UPS unit names would require a new C program. This would be a good programming exercise, but no-one has asked for such a facility in NUT....

...59 4K ip_fib_hash 59 11 18% 0.06K 1 59 4K ip_fib_alias 53 53 100% 0.07K 1 53 4K taskstats_cache 53 1 1% 0.07K 1 53 4K inotify_watch_cache 48 48 100% 0.16K 2 24 8K sigqueue 48 8 16% 0.08K 1 48 4K crq_pool 45 27 60% 0.25K 3 15 12K mnt_cache 45 29 64% 0.25K 3 15 12K dquot 45 32 71% 0.25K 3 15 12K sgpool-8 40 19 47% 0.19K 2 20...

...acpi_parse_ext 0 0 44 84 1 acpi_parse 0 0 28 127 1 acpi_state 0 0 48 78 1 delayacct_cache 183 390 48 78 1 taskstats_cache 9 32 236 16 1 proc_inode_cache 49 170 372 10 1 sigqueue 96 135 144 27 1 radix_tree_node 16046 16786 276 14 1 bdev_cache 56 56 512 7 1 sysfs_dir_cache 4831 4876 40 92 1 mnt_cache 30 60 128 30 1 inode_cache 1041 1276 356 11 1 dentry_c...

On Tue, 21 Mar 2017, Arnaud Quette wrote: > Hi Roger, > > reviving this discussion, since we have a Github ticket for 2.7.5: > https://github.com/networkupstools/nut/issues/293 ... > I've made some additions to clarify things on the timer, and complete the script: > https://github.com/networkupstools/nut/compare/upssched-doc?expand=1 Hi Arnaud, Your change to the

...1 59 4K ip_fib_hash 59 11 18% 0.06K 1 59 4K ip_fib_alias 53 53 100% 0.07K 1 53 4K taskstats_cache 53 1 1% 0.07K 1 53 4K inotify_watch_cache 48 48 100% 0.16K 2 24 8K sigqueue 48 8 16% 0.08K 1 48 4K crq_pool 45 27 60% 0.25K 3 15 12K mnt_cache 45 29 64% 0.25K 3 15 12K dquot 45 32 71% 0.25K 3 15 12K sgpool-8 40 19 47% 0.19K 2 20...

Hi Maxence, > Fyi, i've updated to 4.7.1, the dbcheck still not fix the broken links, > is the fix you talk about planned for a future release ? > > Our customer reported me, some users have issues when their logon server > is DC1 but not when it's DC2. > > On DC1 some users have access to all shares, some doesn't have any > access at all. actually this last

...ov 05 03:09:02 > data.contoso.com sh[24537]: processus avec le même UID que le > processus actuel nov 05 03:09:02 data.contoso.com sh[24537]: -s, > --signal <sig> envoyer le signal indiqué nov 05 03:09:02 > data.contoso.com sh[24537]: -q, --queue <sig> utiliser > sigqueue(2) au lieu de kill(2) nov 05 03:09:02 data.contoso.com > sh[24537]: -p, --pid afficher les PID sans leur envoyer > de signal nov 05 03:09:02 data.contoso.com sh[24537]: -l, --list > [=<signal>] afficher les noms de signal, ou en convertir un en nom > nov 05 03:09:02 d...

...rsion de nom en PID aux nov 05 03:09:02 data.contoso.com sh[24537]: processus avec le même UID que le processus actuel nov 05 03:09:02 data.contoso.com sh[24537]: -s, --signal <sig> envoyer le signal indiqué nov 05 03:09:02 data.contoso.com sh[24537]: -q, --queue <sig> utiliser sigqueue(2) au lieu de kill(2) nov 05 03:09:02 data.contoso.com sh[24537]: -p, --pid afficher les PID sans leur envoyer de signal nov 05 03:09:02 data.contoso.com sh[24537]: -l, --list [=<signal>] afficher les noms de signal, ou en convertir un en nom nov 05 03:09:02 data.contoso.com sh[2...

...ov 05 03:09:02 > data.contoso.com sh[24537]: processus avec le même UID que le > processus actuel nov 05 03:09:02 data.contoso.com sh[24537]: -s, > --signal <sig> envoyer le signal indiqué nov 05 03:09:02 > data.contoso.com sh[24537]: -q, --queue <sig> utiliser > sigqueue(2) au lieu de kill(2) nov 05 03:09:02 data.contoso.com > sh[24537]: -p, --pid afficher les PID sans leur envoyer > de signal nov 05 03:09:02 data.contoso.com sh[24537]: -l, --list > [=<signal>] afficher les noms de signal, ou en convertir un en nom > nov 05 03:09:02 d...

...140 384 10 1 : tunables 54 27 8 : slabdata 14 14 0 skbuff_head_cache 354 390 256 15 1 : tunables 120 60 8 : slabdata 26 26 0 proc_inode_cache 449 456 336 12 1 : tunables 54 27 8 : slabdata 38 38 0 sigqueue 27 27 148 27 1 : tunables 120 60 8 : slabdata 1 1 0 radix_tree_node 3508 3528 276 14 1 : tunables 54 27 8 : slabdata 252 252 0 bdev_cache 26 28 512 7 1 : tunables 54 27 8 : slabdata...

...2019 2072 1144 28 Acpi-State 255 255 80 51 Acpi-Namespace 1428 1428 40 102 task_delay_info 1704 1704 168 24 taskstats 144 144 328 24 proc_inode_cache 1632 1664 976 16 sigqueue 250 250 160 25 bdev_cache 192 192 1344 24 sysfs_dir_cache 23817 23968 144 28 filp 1807 2400 320 25 inode_cache 1861 2244 912 17 dentry 27252 29440 2...

...4 44 88 44 acpi_operand 637 736 40 92 acpi_parse_ext 0 0 44 84 acpi_parse 0 0 28 127 acpi_state 0 0 48 78 proc_inode_cache 17 48 328 12 sigqueue 54 54 144 27 radix_tree_node 810 1456 276 14 bdev_cache 82 90 448 9 sysfs_dir_cache 13325 13340 40 92 mnt_cache 21 30 128 30 inode_cache 2416 2976 3...

Starting with 3.7 rc1, my workstation seems to loose ram. Up until (and including) 3.6, used-(buffers+cached) was roughly the same as sum(rss) (taking shared into account). Now there is an approx 6G gap. When the box first starts, it is clearly less swappy than with <= 3.6; I can''t tell whether that is related. The reduced swappiness persists. It seems to get worse when I update

Hi Guys, My users are reporting some issues with memory on our lustre 1.8.1 clients. It looks like when they submit a single job at a time the run time was about 4.5 minutes. However, when they ran multiple jobs (10 or less) on a client with 192GB of memory on a single node the run time for each job was exceeding 3-4X the run time for the single process. They also noticed that the swap space

I''m trying to do some userspace tracing on a server-process with the pid provider. My problem is, that the only probes the pid-provider lists for the server-process (to which I attach dtrace with "-p nnnn") are coming from "ld.so.1". There''s not a single one from my modules. If I''m specifying "a.out" (or any of our shared-objects) as the

Hey Jens, Please in your spare time (if there is such a thing at a conference) pull this branch: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-3.10 for your v3.10 branch. Sorry for being so late with this. <blurb> It has the ''feature-max-indirect-segments'' implemented in both backend and frontend. The current problem with the backend and