similar to: Improper directory removal causes file system havoc (PR#11738)

This is not general on Solaris 10 -- it works for others, as the R-admin manual told you. What sort of file system is the test being run on? It does look very like a Solaris file system bug. On Wed, 18 Jun 2008, mjbauer at eecs.tufts.edu wrote: > Full_Name: Michael Bauer > Version: 2.7.0 > OS: Solaris 10 (sparc) > Submission from: (NULL) (130.64.21.7) > > > When running

R 2.5.1 compiled, passed the make check and has been successfully running for a couple years on a Sun Fire V490 running Solaris 9. I need a newer version of R, but can't get a newer version of R to pass the make check. I've tried 2.8.1, 2.7.2, 2.6.2 and 2.6.0. (2.5.1 still passes on this server) At this point I thought I'd try to compile it on another Sun server (Solaris 10),

R 2.5.1 compiled, passed the make check and has been successfully running for a couple years on a Sun Fire V490 running Solaris 9. I need a newer version of R, but can't get a newer version of R to pass the make check. I've tried 2.8.1, 2.7.2, 2.6.2 and 2.6.0. (2.5.1 still passes on this server) At this point I thought I'd try to compile it on another Sun server (Solaris 10),

Full_Name: Jim Brown Version: 2.6.0 / 2.6.1 OS: Solaris 10 (SPARC) Submission from: (NULL) (35.8.15.102) I have been able to successfully compile version 2.5.1 using the Sun Studio 12 compilers on Sun Solaris 10 (SPARC). All tests using "make check" pass with a status of OK. However, the following section of "reg-tests-1.R" fails when I attempt to test after a build of

arm64 uses generic syscalls, and does not include the "noat", "noflags", and "deprecated" syscalls. i.e. __ARCH_WANT_SYSCALL_{NO_AT|NO_FLAGS|DEPRECATED} This patch adds the syscalls needed for klibc to run on arm64. Signed-off-by: Steve Capper <steve.capper at linaro.org> --- usr/klibc/Kbuild | 3 +++ usr/klibc/SYSCALLS.def | 33

Commit-ID: 8858e8319655ef38398e0833b71d65b0e620a061 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8858e8319655ef38398e0833b71d65b0e620a061 Author: Steve Capper <steve.capper at linaro.org> AuthorDate: Mon, 11 Nov 2013 17:04:11 +0000 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:31:13 -0800 [klibc] syscalls: Add syscalls

Hello Ervin, The in-memory cache lookup could be added back into samba-4.1.6 by applying the attached patch, if it could be compiled with Louis how-to steps, perhaps got the chance to make U14.04 be stayed on samba-4. Here is my test, the test-bench is uploading 5000 files and each one is 1MB. The attached patch could improve 15% at case B). Case A) Original samba-4.1.6 will go through

Hi. Thanks for good program. I'm quite paranoid guy and dont beleave when some program offer me "use chroot = yes". Instead i jail program manually. I was at 3.0.9 and all was fine. Manual chroot only requires files dir, config and personal tmp. 3.1.1 now also want whole /proc only for /proc/self/fd/X instead just fd number. Whole /proc is serious security risk for me. Why? starce

Hi Jones, many thanks again four your help and your time. Thanks for the patch too - I'll check it up. On my Ubuntu, there is a Samba 4.1.6. I'll install the samba source package, and will try to apply the patch, then - I hope - the package will be compiled as well. I'll notify to you about the result. (First, I need to upgrade that server.) Thanks again, Ervin On Thu, Apr

Hello again, We have hit some performance problem today in one of our clusters. The performance suddenly drop from the normal performance (about 30Mbytes/s), read/write, to a few Kbytes/s (about 200Kbytes/s), read only, for a while, and as sudden as it started, it backs to the normal read/write performance, cycling randomly. When the "read only" occurs on one node, the other shows only

On an i686 with glibc 2.5 installed I'm not able to compile rsync 3.0.2 and later. rsync 3.0.0 was no problem, this compiled. Also on an x86_64 with glibc 2.7 installed rsync compiled. Here is a script of the failing comilation: Script started on Sat May 10 07:33:39 2008 teddy@mail /usr/src/rsync-HEAD-20080508-0612GMT $ mkdir build teddy@mail /usr/src/rsync-HEAD-20080508-0612GMT $ cd build

Hello, I'm testing the "recycle: excludedir" option of Samba recycle bin but for some reason every deleted file is sent to the recycle bin, even those in excluded paths. Using samba/focal-updates,now 2:4.15.13+dfsg-0ubuntu0.20.04.4. This is the config for that share: --- [SHARE1] ??? path = /isp/SHARE1 ??? browseable = no ??? force create mode = 0660 ??? force directory

Enough small fixes have pilled up to make it worth a release: A Google patch adds sched_setaffinity, sched_getaffinity support. Openembedded uses kexec_load(). Gentoo folks add a Kbuild fix. ipconfig no longer wild guesses a nameserver when none is provided by the DHCP server. strndup() and unlinkat() saw fixes for various problems. codingstyle cleanup in kinit and tools. git repository:

Commit-ID: 0c7359e8787c60b7143b3e366d31b2c2409cba3a Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0c7359e8787c60b7143b3e366d31b2c2409cba3a Author: Steve Capper <steve.capper at linaro.org> AuthorDate: Mon, 11 Nov 2013 17:04:10 +0000 Committer: H. Peter Anvin <hpa at zytor.com> CommitDate: Mon, 11 Nov 2013 19:30:11 -0800 [klibc] syscalls: Fixup some of the

everyone, Just out of curiosity, I did a dtrace -n ''syscall:::entry { @num[execname, probefunc] = count(); }'' and looked at the entries produced by ''rm''. I see everything that rm did, *except* the unlinkat - which is unfortunate because I want to trace which processes have deleted which files. So - does dtrace contain unlinkat as a probe for a system call?

Hello All, now that the BUG 14343: (s3: vfs_full_audit: Add missing fcntl entry in vfs_op_names[] array.) was fixed I wanted to try 4.12 again. This is the relevant config which has been running for years: vfs objects = acl_xattr full_audit shadow_copy2 full_audit:failure = none full_audit:success = pwrite write rename unlink full_audit:prefix = IP=%I|USER=%u|MACHINE=%m|VOLUME=%S

Hi Team, We are having compile/linking time warning due unsatisfied system calls and macros. We have checked and confirm that these are not supported by hp-ux kernel and enabling them will require changes in VFS layer and physical filesystem. Unsatisfied system calls * renameat * symlinkat * linkat * unlinkat * readlinkat * mkdirat Undefined

Commit-ID: a311e6839f6e8e9797d0a0bd8e1222d22e10a018 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=a311e6839f6e8e9797d0a0bd8e1222d22e10a018 Author: Martijn Dekker <martijn at inlv.org> AuthorDate: Tue, 6 Mar 2018 17:40:37 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] expand: 'nolog' and

Commit-ID: 8d7c846f252b7eabd7cb7d02e7b53fb5a835402e Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8d7c846f252b7eabd7cb7d02e7b53fb5a835402e Author: Martijn Dekker <martijn at inlv.org> AuthorDate: Tue, 6 Mar 2018 17:40:37 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: expand: 'nolog'

On Fri, 22 Sep 2017 17:04:14 -0500 Paul Johnson wrote: > The bad problem I see now is that Emacs and Chromium-browser, which > rely on gtk3 don't work properly anymore. In Emacs, the symptom is > that the ribbon of buttons under the pull down menu will no longer > show. In Chromium, the buttons and other widget things on the top > are an ugly yellow distortion. Un-intuitive