From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: RE: [Bluez-devel] Problems with smart phones when using a"silent"kernel
Date: Mon, 16 Jan 2006 17:21:50 +0100 [thread overview]
Message-ID: <1137428510.6324.58.camel@localhost.localdomain> (raw)
In-Reply-To: <C70061B183DE09419568AB2060C52A950177D435@arion.intra.local>
Hi Victor,
> This fixes the problem with console redirected to /dev/null.
I applied your patch to the CVS, but is this the best way to redirect
stdin, stdout and stderr to /dev/null?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-01-16 16:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 15:13 [Bluez-devel] Problems with smart phones when using a"silent"kernel Victor Shcherbatyuk
2006-01-16 16:17 ` Dimitry Andric
2006-01-16 16:21 ` Marcel Holtmann [this message]
2006-01-16 17:27 ` Bastien Nocera
-- strict thread matches above, loose matches on Subject: below --
2006-01-17 10:07 Victor Shcherbatyuk
2006-01-17 10:43 ` Marcel Holtmann
2006-01-13 13:01 Victor Shcherbatyuk
2006-01-13 11:39 [Bluez-devel] Problems with smart phones when using a "silent"kernel Victor Shcherbatyuk
2006-01-13 12:13 ` Marcel Holtmann
2006-01-12 13:35 Victor Shcherbatyuk
2006-01-12 10:19 [Bluez-devel] Problems with smart phones when using a "silent" kernel Victor Shchebatyuk
2006-01-12 13:27 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1137428510.6324.58.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).