similar to: $stderr and $stdout are send as part of http response

Hi, I am using Ruby 1.8.3 and Rails 0.14.2, running on Linux (Fedora) and lighttpd. When there is an exception during RSS parsing or Webservice call, I am getting the error messages shown on the browser. This happens only when there is an exception thrown. This happens only on Linux, not on windows server. lighttpd has write access to the log files. Am I missing some configuration or

Hi friends, I''m facing a very strange problem... I consume a webservice from within my rails app. I''ve written a thin wrapper around the webservice using Net::HTTP.post_form However, when calling the API from within my controllers, the API calls randomly fail, complaining about timeout. But - when I wrote a simple iterative test (500 iterations), calling the same webservice

Hi all. The old (~3.6.x) PAM code used to send PAM messages to stderr, whereas the new generic loginmsg code sends them to stdout, and it sends an extra newline. I think stderr is probably right, but the extra \n should probably be removed either way. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with

Hi, recover() sends all its messages, which I consider to be error messages, to stdout. I think they more properly belong to stderr. This is an important difference for those of us who use R in batch mode to generate ASCII files. Thanks, Vadim [[alternative HTML version deleted]]

https://bugzilla.samba.org/show_bug.cgi?id=4320 Summary: Daemon should send stdout, stderr of {pre,post}-xfer command to client Product: rsync Version: 3.0.0 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org

I''m using ActionWebService to expose a WebService of my application, and I would like to control the error responses sent back to the client. At very least, I would like to prevent the XML to include the backtrace. How can I do this?

Dear List, I want to run a rsync-ing script in cron, generating a very verbose -vv rsync log in a log file. The log file should combine both stderr and stdin, which is easy: backup.sh >>/var/log/backup.log 2>&1 However, I would like to propagate only stderr to cron - in case there has been an error, cron will mail me the assembled stderr output. I tried the following: $

"Alexander Georgiev" <alexander.georgiev at gmail.com> wrote: > I want to run a rsync-ing script in cron, generating a very verbose > -vv rsync log in a log file. The log file should combine both stderr > and stdin, which is easy: > > backup.sh >>/var/log/backup.log 2>&1 > > However, I would like to propagate only stderr to cron - in case

The attached patch against today's CVS improves write() error handling and logging in clientloop.c when flushing stdout/stderr. -- Carson Gaspar - carson at taltos.org Queen trapped in a butch body -------------- next part -------------- A non-text attachment was scrubbed... Name: clientloop.c.diff Type: application/octet-stream Size: 966 bytes Desc: not available Url :

https://bugzilla.mindrot.org/show_bug.cgi?id=773 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #4 from Damien Miller <djm at

Apparent newer versions of that report everything on stdout, including error messages; since we only print something on failure, fold stdout to stderr so we can see everything on failure. --- daemon/xfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daemon/xfs.c b/daemon/xfs.c index abc2736..7f72e6a 100644 --- a/daemon/xfs.c +++ b/daemon/xfs.c @@ -537,7 +537,7 @@

$ ./nbdkit ssh host=localhost /nosuchfile password=-0 --run 'qemu-img info $nbd' abc fcntl: Bad file descriptor The reason for this is that we close the file descriptor after reading the password. Closing stdin causes bad stuff to happen. --- docs/nbdkit-plugin.pod | 5 +++++ server/public.c | 4 ++-- 2 files changed, 7 insertions(+), 2 deletions(-) diff --git

hi, I've created a small script to get a sum from the users and sessions (table username and table "#"), but it is annoying that the headline "username # proto (pids) (ips)" goes to STDERR, but the normal output to STDOUT. It would be nice, if both goes to the same STD :-) cu denny -------------- next part -------------- A non-text attachment was scrubbed... Name:

Hi all. I'm writing an installation script that uses Cygwin's bash.exe to launch an rsync.exe process, which is passed arguments. This performs an rsync over the Internet. I'd like to capture stdout to one file, and stderr to another, so that I can have a clean log of any errors. However, rsync.exe's use of file descriptors isn't jiving with my understanding of them. If I

Contrary to other functions in 'base', attach() output messages to stdout instead of stdout, e.g. > a <- 1 > capture.output(attach(list(a=1))) [1] "The following object is masked _by_ .GlobalEnv:" [2] "" [3] " a" Shouldn't this message go to stderr? Here's a patch for the local function checkConflicts() of base::attach(), cf. ditto for

Why do you need this? The sink system is often specifically needed to capture such messages and display them to the user, for example in an embedded environment. Many applications would not work when you bypass the stdout/stderr set by the system. For example tools like knitr or rapache need to capture stdout to get the output and insert it in a report or webpage. If you really want to, perhaps

It seems that under Windows, some UTF-8 strings that print OK to stdout do not print correctly to stderr. To reproduce: x <- "\ub124" cat(x, file = stdout()) ## ? cat(x, file = stderr()) ## <U+B124> Original motivating problem here: https://stackoverflow.com/questions/32696241/how-to-display-a-message-warning-error-with-unicode-characters-under-windows How does printing to

Hi! I want to pipe stdout/stderr from vorbize for wrapper scripts. But as it doesn't send any "\n"s it doesn't work correctly. I solved it by adding if (param.verbose == 1) { fprintf (stderr, "\n"); } into appropriate position in vorbize.c. Could somebody please implement this nicely? Something like "-e" option in cdparanoia. Thnx. Bye, Peter Surda

Hello, There appears to be an error in the stderr redirection of the crontab rsync entry. In Bourne shell and compatibles (crontab entries are run by the Bourne shell) redirections are processed from left to right and "2>&1" redirects the stderr to the same location stdout is currently directed and not to stdout. Hence: cmd 2>&1 > log directs stderr to the

http://bugzilla.mindrot.org/show_bug.cgi?id=773 Summary: OpenSSH hangs or silently exits on write failure on stdout/stderr Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-bugs