This is for automatic-rename. I bet you only have one window open and the process running in it is pid 31986.
Bump NAME_INTERVAL if you want it to do it less often but automatic-rename will be less responsive. On Sat, Jul 23, 2011 at 07:40:15PM -0700, Robin Lee Powell wrote: > > Discovered this working on a tmux-related selinux issue, > https://bugzilla.redhat.com/show_bug.cgi?id=723391 ; apparently tmux > really really really wants to know what command line it was run > with, since it checks about 2 times a second: > > > 19:39:14 munmap(0x2b42928aa000, 4096) = 0 > 19:39:14 gettimeofday({1311475154, 954092}, NULL) = 0 > 19:39:14 clock_gettime(CLOCK_MONOTONIC, {251379, 405689220}) = 0 > 19:39:14 clock_gettime(CLOCK_MONOTONIC, {251379, 405745561}) = 0 > 19:39:14 epoll_wait(3, {}, 32, 500) = 0 > 19:39:15 clock_gettime(CLOCK_MONOTONIC, {251379, 906648285}) = 0 > 19:39:15 ioctl(14, TIOCGPGRP, [31986]) = 0 > 19:39:15 open("/proc/31986/cmdline", O_RDONLY) = 15 > 19:39:15 fstat(15, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 > 19:39:15 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, > -1, 0) = 0x2b42928aa000 > 19:39:15 read(15, "-zsh\0", 1024) = 5 > 19:39:15 close(15) = 0 > 19:39:15 munmap(0x2b42928aa000, 4096) = 0 > 19:39:15 gettimeofday({1311475155, 455923}, NULL) = 0 > 19:39:15 clock_gettime(CLOCK_MONOTONIC, {251379, 907520794}) = 0 > 19:39:15 clock_gettime(CLOCK_MONOTONIC, {251379, 907577421}) = 0 > 19:39:15 epoll_wait(3, {}, 32, 479) = 0 > 19:39:15 clock_gettime(CLOCK_MONOTONIC, {251380, 387449801}) = 0 > 19:39:15 gettimeofday({1311475155, 936009}, NULL) = 0 > 19:39:15 gettimeofday({1311475155, 936069}, NULL) = 0 > 19:39:15 clock_gettime(CLOCK_MONOTONIC, {251380, 387665717}) = 0 > 19:39:15 clock_gettime(CLOCK_MONOTONIC, {251380, 387721961}) = 0 > 19:39:15 epoll_wait(3, {}, 32, 19) = 0 > 19:39:15 clock_gettime(CLOCK_MONOTONIC, {251380, 407052034}) = 0 > 19:39:15 ioctl(14, TIOCGPGRP, [31986]) = 0 > 19:39:15 open("/proc/31986/cmdline", O_RDONLY) = 15 > 19:39:15 fstat(15, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 > 19:39:15 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, > -1, 0) = 0x2b42928aa000 > 19:39:15 read(15, "-zsh\0", 1024) = 5 > 19:39:15 close(15) = 0 > 19:39:15 munmap(0x2b42928aa000, 4096) = 0 > 19:39:15 gettimeofday({1311475155, 956228}, NULL) = 0 > 19:39:15 clock_gettime(CLOCK_MONOTONIC, {251380, 407825222}) = 0 > 19:39:15 clock_gettime(CLOCK_MONOTONIC, {251380, 407881421}) = 0 > 19:39:15 epoll_wait(3, {}, 32, 500) = 0 > 19:39:16 clock_gettime(CLOCK_MONOTONIC, {251380, 908835989}) = 0 > 19:39:16 ioctl(14, TIOCGPGRP, [31986]) = 0 > 19:39:16 open("/proc/31986/cmdline", O_RDONLY) = 15 > 19:39:16 fstat(15, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 > 19:39:16 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, > -1, 0) = 0x2b42928aa000 > 19:39:16 read(15, "-zsh\0", 1024) = 5 > 19:39:16 close(15) = 0 > 19:39:16 munmap(0x2b42928aa000, 4096) = 0 > 19:39:16 gettimeofday({1311475156, 458165}, NULL) = 0 > 19:39:16 clock_gettime(CLOCK_MONOTONIC, {251380, 909767944}) = 0 > 19:39:16 clock_gettime(CLOCK_MONOTONIC, {251380, 909827694}) = 0 > 19:39:16 epoll_wait(3, {}, 32, 478) = 0 > 19:39:16 clock_gettime(CLOCK_MONOTONIC, {251381, 388909058}) = 0 > 19:39:16 gettimeofday({1311475156, 937469}, NULL) = 0 > 19:39:16 gettimeofday({1311475156, 937696}, NULL) = 0 > 19:39:16 clock_gettime(CLOCK_MONOTONIC, {251381, 389299336}) = 0 > 19:39:16 clock_gettime(CLOCK_MONOTONIC, {251381, 389389944}) = 0 > 19:39:16 epoll_wait(3, {}, 32, 20) = 0 > 19:39:16 clock_gettime(CLOCK_MONOTONIC, {251381, 409857562}) = 0 > 19:39:16 ioctl(14, TIOCGPGRP, [31986]) = 0 > 19:39:16 open("/proc/31986/cmdline", O_RDONLY) = 15 > 19:39:16 fstat(15, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 > 19:39:16 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, > -1, 0) = 0x2b42928aa000 > 19:39:16 read(15, "-zsh\0", 1024) = 5 > 19:39:16 close(15) = 0 > > > Probably not a big deal, but rather odd. > > -Robin > > ------------------------------------------------------------------------------ > Magic Quadrant for Content-Aware Data Loss Prevention > Research study explores the data loss prevention market. Includes in-depth > analysis on the changes within the DLP market, and the criteria used to > evaluate the strengths and weaknesses of these DLP solutions. > http://www.accelacomm.com/jaw/sfnl/114/51385063/ > _______________________________________________ > tmux-users mailing list > tmux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tmux-users ------------------------------------------------------------------------------ Magic Quadrant for Content-Aware Data Loss Prevention Research study explores the data loss prevention market. Includes in-depth analysis on the changes within the DLP market, and the criteria used to evaluate the strengths and weaknesses of these DLP solutions. http://www.accelacomm.com/jaw/sfnl/114/51385063/ _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
