search for: _testing_

Hello all, There is kernel-smp-2.6.9-48 from Jason Baron at http://people.redhat.com/~jbaron/rhel4/ Can anyone advice where I can find RPMs of this kernel version for CentOS 4.4 ? Or how it can be created... -- Best regards, Maxim mailto:maxim at osetia.org

Hey folks, Is there any way to exit an mclapply early on error? For example, in the following mclapply loop, I have to wait for all the processes to finish before the error is returned. ``` mclapply(X = 1:12, FUN = function(x) {Sys.sleep(0.1); if(x == 4) stop()}, mc.cores = 4, mc.preschedule = F) ``` When there are many calculations in FUN, it takes a long time before the error is returned.

...} )) } res <- lapply_with_error..8(X = 1:12, FUN = function(x) {Sys.sleep(0.1); if(x == 4) stop()}) Then we can investigate the problem for the element that generated errors. It is even better if we could anticipate the errors and avoid surprises by well _testing_ the function before launching a long process. If you want the processes to fail fast, I fear that you want to launch the parallel process too soon without having tested your function enough. HTH, Jeremie

...are Always Learning about good security practices and emerging threats to the OS. The root password is close to, if not actually, our last line of defense (SELinux helps us here by the way). Using a one character password is problematic if you are connected to the internet, for example, if you are _testing_ the OS and want to run updates after the install. This is problematic since, by default, new installs typically allows SSH access and root logins over SSH. Yes, firewalls help, but they need to be configured correctly, and there are subtle tricks that sophisticated attackers can exploit to subvert...

There is a central assertion to this argument that I don't follow: > At the end of the day most published results obtained with R just won't be reproducible. This is a very strong assertion. What is the evidence for it? I write a lot of Sweave/knitr in house as a way of documenting complex analyses, and a glm() based logistic regression looks the same yesterday as it will

On Mon, 2015-02-02 at 15:17 -0700, Warren Young wrote: > The answer is clear to me: general security principles. By the time EL8 comes out, we?ll have had ~3 years of warnings under EL7 that weak passwords would not be tolerated, and they?re finally disallowing them. Good! > > (More like 6 years, actually, because EL6 gives a red warning bar for weak passwords.) > > Let?s flip

...d amend the reports using /etc/logwatch ...). Read the logs. Allocate file and directory permissions to users lacking any log-on ability. There is a lot that can be done. > Using a one character > password is problematic if you are connected to the internet, for > example, if you are _testing_ the OS and want to run updates after the > install. But if one is doing things on a isolated machine unconnected to anything why the password aggro ? Best never to speculate when attempting to justify a hash and arrogant policy of DO WHAT RHEL DEMANDS. I prefer a clear warning and then let th...

Le Mercredi 5 Juillet 2006 09:41, Dirk Eddelbuettel a ?crit?: > Salut Vincent, > > On 4 July 2006 at 23:27, Vincent Goulet wrote: > | I'm currently following your procedure suggested on R-SIG-Debian > | (https://stat.ethz.ch/pipermail/r-sig-debian/2006-June/000095.html) to > | compile and install the latest version of R on Kubuntu. It is my > | understanding that I