similar to: Runit

Hi, I''m deploying Unicorn on a Rails application with RUnit. Technically I''m using Chef''s deployment tools, if any of you are familiar with it (https://github.com/opscode-cookbooks/application_ruby) but to be clear they aren''t doing anything magical, so this is purely an issue with RUnit and Unicorn. The TL;DR of the following post, which has lots of

Hey, I''m using mongrel supervised via runit. I''d like to capture mongrel logs with svlogd, which just requires logging to stdout/stderr. But, the Rails app is logging in its own log directory. Is there a way to make both mongrel and Rails log to stdout/stderr? Thanks, Mike -- Michael P. Soulier <msoulier at digitaltorque.ca> "Any intelligent fool can make things

I''d like to announce the first release of capistrano-runit-tasks. This came about as I wanted to use runit rather than spinner/spawner/ reaper on my memory limited VPS but should be useable for any setup. From the README: This library extends Capistrano to allow processes to be supervised using the runit package. It replaces some of the standard tasks with runit versions and

I''d like to announce the second release of capistrano-runit-tasks, available from http://rubyforge.org/projects/cappy-runit/ It now supports: * File based templates * sv as the service control command in addition to runsvctrl * A much simpler interface for creating additional services. More work still needs to be done though! == TODO * Allow add_service to create more than one

Hello, I have mongrel_rails supervised via runit, and it would be helpful if it could log everything to stdout so it can be captured with svlogd. Is it possible to tell mongrel to log everything to stdout? What about rails? Thanks, Mike -- Michael P. Soulier <msoulier at digitaltorque.ca> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius -

I'm running dovecot under runit: #!/bin/sh echo '/var/core/%p' > /proc/sys/kernel/core_pattern ulimit -n 8096 ulimit -c unlimited exec /usr/local/sbin/dovecot -F (that way, together with incron, I can automatically generate the coredumps I'm posting all the time) If I apply a patch and recompile, what is the fastest way of restarting dovecot? Which part of the process

Hello! I have looked at Martin's recent work on "merging" unit tests with R CMD check, fused it with my and Tony's contributions and developed it a bit further. Take a look into the attached demo package on how it works. In essence: PKG/inst/RUnitTests |- runRUnitTests.R (script to run RUnit tests) \- ... (any RUnit test file)

Folks, An RUnit test suite is failing after all tests are complete with the following message: Error in parse(n = -1, file = file) : unexpected '}' at 620: 621: } All individual tests work when run individually, and all but one run within the RUnit test suite. What might be causing this? A similar error message during package creation was discussed earlier

Hi! I appologize for crossposting, but this might be of broader interest. In case you are interested in fusing RUnit with R CMD check under unix alike OS, here is one way of doing/hacking this. My aim was to perform unit tests: (1) during R CMD check (2) at any other time Say you have a package PKG in a map PKG. I use the following structure PKG |- R |- ... |- inst | |- doc | `-

R-developers Does anybody know how I incorporate the use of the tracker in RUnit in the unit tests? I have read the RUnit Vignette, help pages and searched around, but I could find no examples of using 'inspect' in the unit test functions. Moreover, doing so, I tried something like library(RUnit) myFunction <- function(x) { return(x) } track <- tracker() track$init()

Having used JUnit and PyUnit, I was pleased to see the release of the RUnit package on CRAN. I'm wondering if there are any RUnit users out there that would be willing to share some tips on how they organize their code to work with RUnit. Specifically, I'm wondering about the best way to load/import/source the functions to be tested. I would like to end up with a script, testall or some

I made my own RUnit testing convention, and I want to introduce this to one of my friends. Before that, I'd like to review my codes. The problem that I met when I tried to polish my codes is: How can I get the file path in the file??? I.e., I want to get the path to the file that I'm writing using some magic R functions. But I couldn't find any good magic. Is there any magic? So, I

There appears to be a bug in RUnit. Given a testsuite testsuite.math, say, when I run: runTestSuite(testsuite.math) this works fine, provided there are no extraneous files in the unit test subdirectory. But if there are any Emacs temp files (with names that end with '~') then runTestSuite gets confused and tries to run functions from the temp files as well. [[alternative HTML version

We would like to announce the availability on CRAN of a new package: RUnit It contains a unit testing framework strongly inspired by Javas popular JUint package. In addition it contains some functionality to investigate the degree to which some function is covered by a test suite. The main aims of the package are - to support a development style where test cases are written and constantly

We would like to announce the availability on CRAN of a new package: RUnit It contains a unit testing framework strongly inspired by Javas popular JUint package. In addition it contains some functionality to investigate the degree to which some function is covered by a test suite. The main aims of the package are - to support a development style where test cases are written and constantly

Package: logcheck Version: 1.2.41 Problem: Logcheck try to detect if log file have been rotate or not by file size way. Possible attack: - current log file (sizeA) - run logcheck, (logcheck/logtail put inode in offsetfile), offset=sizeA - [attacker run attack 1] - run logrotate - [attacker run attack 2] - run logcheck may don't detect the rotation and don't check the log for attack 1

Package: logcheck Version: 1.2.58.0 Severity: wishlist Tags: patch The attached patch is the diff from current svn trunk to my svn branch zugschlus200707. It introduces a new binary package logtail2 with a new binary logtail2 which enhances logtail substantially. logtail2 can process rotated logs internally, which makes the code inside logcheck and other programs that use logtail2 easier to

Package: logcheck Version: 1.3.13 Severity: normal Hi, at present my logcheck is into 33 minutes of cpu time for running the ignore/innd rule, when the innd package is not installed. If running logcheck against only locally created logfiles, there should be a configuration option to only run logcheck against installed (or non-purged) packages. -- System Information: Debian Release: squeeze/sid

commit 81496d0cf7b161bf981d51f0b96f860d68f3f6e3 Author: Micah Anderson <micah at debian.org> Date: Fri Aug 24 17:51:31 2007 -0400 Enable alternate temporary directory to be set in the configuration file On servers where the logfiles are very large and grow quickly, the logcheck processes may run into space issues in /tmp resulting in the email such as the following to be

Package: logcheck Version: 1.3.14 Severity: normal Tags: patch I keep getting these messages logged, when under high load. This patch should clean that up. commit 72661acccafa519fcb48a6a756e5c35d96e7511d Author: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn at axis.com> Date: Fri Jan 27 16:08:33 2012 +0100 Workaround for error: /usr/sbin/logcheck: line 100: kill: (31667)