search for: rlim_infinity

...ed ...> --- SIGRTMIN (Unknown signal 32) @ 0 (0) --- <... rt_sigsuspend resumed> ) = -1 EINTR (Interrupted system call) sigreturn() = ? (mask now [RTMIN]) waitpid(21423, NULL, __WCLONE) = 21423 close(4) = 0 close(3) = 0 getpid() = 21422 getrlimit(RLIMIT_STACK, {rlim_cur=2044*1024, rlim_max=RLIM_INFINITY}) = 0 setrlimit(RLIMIT_STACK, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 rt_sigaction(SIGRTMIN, {SIG_DFL}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {SIG_DFL}, NULL, 8) = 0 rt_sigaction(SIGRT_2, {SIG_DFL}, NULL, 8) = 0 execve("/usr/local/bin/wine-preloader", ["/usr/local/bin/wi...

...king for cc configure:1471: found /usr/bin/cc configure:1481: result: cc configure:1645: checking for C compiler version configure:1648: cc --version </dev/null >&5 cc: 1501-216 command option -version is not recognized - passed to ld Warning: Hard ulimit has been reduced to less than RLIM_INFINITY. = There may not be eno ugh space to complete the compilation. C for AIX Compiler, Version 5 -------------------------------------------------------------------------= ----------------------------------------- configure:1661: $? =3D 249 configure:1687: checking for C compiler default output co...

Has anyone tried LFS (ie >2G files support) and Ext3 together? Are there good reasons why this should/should not work? I see the RH enterprise kernel patch set specifically does not attempt both lfs and ext3, but the lfs patches themselves touch some reasonably localised parts of ext2, so I would hope (without having dived in there to test), that the ext3 changes would mirror that

Hi, we're in the process of setting up large-page support on IBM regattas, but for large-page support the users have to have a set of extra capabilities (CAP_BYPASS_RAC_VMM,CAP_PROPAGATE). This are configured on a per user basis by listing which capability each user have in /etc/security/user. Unfortunately they don't get set when the users log in via OpenSSH (3.1p1). Does anybody know

...2) = 0 set_tid_address(0x402ff708) = 21587 rt_sigaction(SIGRTMIN, {0x4003a760, [], SA_SIGINFO}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {0x4003a3a0, [], SA_RESTART|SA_SIGINFO}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 _sysctl({{CTL_KERN, KERN_VERSION}, 2, 0xbffff17c, 31, (nil), 0}) = 0 brk(0) = 0x812c000 brk(0x814d000) = 0x814d000 uname({sysname="Linux", nodename="hermes", release="2.6.11.4-21.9-defau...

This is a repost of a previously posted set. It's been updated following review comments. [PATCH 1/4] Add a core_pattern debug command Added missing return statements. [PATCH 2/4] Call sync after guestfsd exits Remove redundant sleep 1; sync [PATCH 3/4] Shut down the appliance cleanly [PATCH 4/4] Ignore launch() error in virt-rescue These were previously 2 patches. They are otherwise

[PATCH 1/3] Add a core_pattern debug command The first patch is just a rework of Rich's earlier core dump patch. It turns it into a debug subcommand so it can be called at any time. This also has the advantage of explicitly labelling an extremely untidy API as debug. [PATCH 2/3] Call sync after guestfsd exits The second patch seems to be required for cores to be dumped reliably. I was able to

http://bugzilla.mindrot.org/show_bug.cgi?id=354 ------- Additional Comments From cjwatson at debian.org 2003-01-03 02:42 ------- Alternatively, perhaps sshd could be configured to setrlimit() everything up to RLIM_INFINITY after forking but before giving up root privileges. It could then rely on pam_limits to set limits back down if the administrator wants that, which would work even with session modules run as non-root. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are...

...0); with same results on 5.1-R(0 byte core file) and 4.4-R(get a core usable with gdb). - "ulimit -a" on the 5.1-R machine gives core file size (blocks, -c) unlimited - Just to be sure I used getrlimit() to find what this limit is for RLIMIT_CORE im my processes, and it is RLIM_INFINITY. - I did the basic checks like write permission on current directory, it looks fine. Can someone help me resolve this? Thanks, Yogeshwar.

...(0x76f86070, 0xc) = 0 rt_sigaction(SIGRTMIN, {0x76f568e8, [], SA_SIGINFO|0x4000000}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {0x76f56794, [], SA_RESTART|SA_SIGINFO|0x4000000}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 ioctl(0, SNDCTL_TMR_TIMEBASE or TCGETS, {B115200 opost isig icanon echo ...}) = 0 ioctl(1, SNDCTL_TMR_TIMEBASE or TCGETS, {B115200 opost isig icanon echo ...}) = 0 write(1, "Network UPS Tools - UPS driver c"..., 51Network UPS Tools - UPS driver controller 1.01-900 ) = 51 brk(0)...

...(0xb7dc5b10, 0xc) = 0 > rt_sigaction(SIGRTMIN, {0xb7ef66d0, [], SA_SIGINFO}, NULL, 8) = 0 > rt_sigaction(SIGRT_1, {0xb7ef6750, [], SA_RESTART|SA_SIGINFO}, NULL, 8) = 0 > rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 > getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 > uname({sys="Linux", node="portege", ...}) = 0 > brk(0) = 0x8b2d000 > brk(0x8b4e000) = 0x8b4e000 > setrlimit(RLIMIT_CORE, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 > open("/tmp/glust...

...GRTMIN, {0x7ff03dd0dad0, [], SA_RESTORER|SA_SIGINFO, 0x7ff03dd17030}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {0x7ff03dd0db60, [], SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x7ff03dd17030}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 getuid() = 1000 brk(0) = 0x1eb8000 brk(0x1ee1000) = 0x1ee1000 uname({sys="Linux", node="pathi", ...}) = 0 rt_sigaction(SIGPIPE, {SIG_IGN, [], SA_RESTORER|SA_RESTART, 0x7ff03df56480}, N...

...y:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0 munmap(0x40018000, 122568) = 0 set_tid_address(0x4017c2e8) = 23015 rt_sigaction(SIGRTMIN, {0x4016c950, [], SA_SIGINFO}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 _sysctl({{CTL_KERN, KERN_VERSION}, 2, 0xbfffdd98, 35, (nil), 0}) = 0 open("/proc/mounts", O_RDONLY) = 3 brk(0) = 0x805b000 brk(0x807d000) = 0x807d000 read(3, "rootfs / rootfs rw 0 0\n/dev...

...on(SIGRTMIN, {0x3e73a053c0, [], SA_RESTORER|SA_SIGINFO, 0x3e73a0eca0}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {0x3e73a052f0, [], SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x3e73a0eca0}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=10240*1024, rlim_max=RLIM_INFINITY}) = 0 brk(0) = 0x4ad2000 brk(0x4af3000) = 0x4af3000 epoll_create(64) = 3 writev(2, [{"ldbsearch", 9}, {": ", 2}, {"symbol lookup error", 19}, {": ", 2}, {"/usr/lib64/libldb...

https://bugzilla.mindrot.org/show_bug.cgi?id=3581 Bug ID: 3581 Summary: ssh-keyscan fails with `fdlim_get: bad value` with large file descriptor limit due to type confusion Product: Portable OpenSSH Version: 9.3p1 Hardware: ARM64 OS: Mac OS X Status: NEW Severity: enhancement

Any user with shell access, or with access to upload a cgi script can exploit this to make machine thrash badly. Seems to circumvent any limits in the kernel Here are my settings dlai@whale.home.org:/home/dlai?limit cputime unlimited filesize 20000 kbytes datasize 8192 kbytes stacksize 8192 kbytes coredumpsize 1000000 kbytes memoryuse 8192 kbytes descriptors

...58585) = 0 set_tid_address(0x4044c0c8) = -1 ENOSYS (Function not implemented) rt_sigaction(SIGRTMIN, {0x40260620, [], SA_RESTORER|SA_SIGINFO, 0x40266e40}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 rt_sigaction(SIGINT, {0x40230290, ~[RTMIN], SA_RESTORER, 0x40266e48}, NULL, 8) = 0 rt_sigaction(SIGTERM, {0x40230290, ~[RTMIN], SA_RESTORER, 0x40266e48}, NULL, 8) = 0 rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0 rt_sigaction(SIGHUP, {SIG_DFL}, NULL, 8) = 0 rt_sigprocmask(SIG_BLOCK, [HUP IN...

Dear R devs, For some days now (~ February, 4th), I am not able to build the recent tarballs of R-devel on a FreeBSD test box anymore. The breakage seems to be related to the newest overhaul of src/unix/system.c: [..snip..] gcc49 -std=gnu99 -I. -I../../src/include -I../../src/include -I/usr/local/include -DLIBICONV_PLUG -I/usr/local/include -isystem /usr/local/include -DHAVE_CONFIG_H -fopenmp

On Sat, Sep 5, 2015 at 11:50 AM, Greg Stark <stark at mit.edu> wrote: > On Sat, Sep 5, 2015 at 6:38 PM, Kostya Serebryany <kcc at google.com> wrote: > > > > This is more like a limitation of asan, not libFuzzer. > > By design, asan does not recover from the first crash. > > This feature has been criticized quite a lot, but I am still convinced > this >

...tion(SIGRTMIN, {0x3eae205380, [], SA_RESTORER|SA_SIGINFO, 0x3eae20eb10}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {0x3eae2052b0, [], SA_RESTORER|SA_RESTART|SA_SIGINFO, 0x3eae20eb10}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=10240*1024, rlim_max=RLIM_INFINITY}) = 0 brk(0) = 0x1bb97000 brk(0x1bbc0000) = 0x1bbc0000 uname({sys="Linux", node="director1", ...}) = 0 rt_sigaction(SIGPIPE, {0x1, [], SA_RESTORER|SA_RESTART, 0x3eada302d0}, NULL, 8) = 0 rt_sigaction(SIGALRM, {0x31c7648b40...