Marcel,
This fixes the problem with console redirected to /dev/null.
Regards,
Victor.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Victor
Shcherbatyuk
Sent: Friday, January 13, 2006 14:02 PM
To: [email protected]
Subject: RE: [Bluez-devel] Problems with smart phones when using
a"silent"kernel
I've checked, it is running, so the only option it has some issues with
console redirected to /dev/null... Will check the logs...
Regards,
Victor.
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Marcel
Holtmann
Sent: Friday, January 13, 2006 13:13 PM
To: [email protected]
Subject: RE: [Bluez-devel] Problems with smart phones when using
a"silent"kernel
Hi Victor,
> Small update. I've tried to connect with rfcomm tool - the same
> behaviour. With the silent kernel it does not connect to Windows
> Mobile phones. The logs show attempts to connect to the phone with
"normal"
> kernel (connection successful) and "silent" one (fails). PSM Not
> Supported is something that probably goes wrong...
these stupid Microsoft devices. Everytime they get a connection, they
connect back to the SDP server of that device and this fails. So it
seems to me that the SDP daemon is not running or have problems with the
console redirected to /dev/null. Check in the log files for errors from
sdpd. Or you might need to use strace to track it.
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
This e-mail message contains information which is confidential and may
be privileged. It is intended for use by the addressee only. If you are
not the intended addressee, we request that you notify the sender
immediately and delete or destroy this e-mail message and any
attachment(s), without copying, saving, forwarding, disclosing or using
its contents in any other way. TomTom N.V., TomTom International BV or
any other company belonging to the TomTom group of companies will not be
liable for damage relating to the communication by e-mail of data,
documents or any other information.
-------------------------------------------------------
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_idv37&alloc_id865&op=ick
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
This e-mail message contains information which is confidential and may be privileged. It is intended for use by the addressee only. If you are not the intended addressee, we request that you notify the sender immediately and delete or destroy this e-mail message and any attachment(s), without copying, saving, forwarding, disclosing or using its contents in any other way. TomTom N.V., TomTom International BV or any other company belonging to the TomTom group of companies will not be liable for damage relating to the communication by e-mail of data, documents or any other information.
On Mon, 2006-01-16 at 17:21 +0100, Marcel Holtmann wrote:
> 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?
As Dimitry mentioned, daemon(3) should help:
Unless the argument noclose is non-zero, daemon() will redirect
stan-
dard input, standard output and standard error to /dev/null.
---
Bastien Nocera <[email protected]>
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Victor Shcherbatyuk wrote:
> This fixes the problem with console redirected to /dev/null.
---snip---
> + dup2(fd, STDIN_FILENO);
> + dup2(fd, STDOUT_FILENO);
> + dup2(fd, STDERR_FILENO);
Heheh, yet another reason to always use daemon(3) instead of rolling your own!