public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bluez-utils 2.7 default configuration
Date: Tue, 01 Jun 2004 00:22:08 +0200	[thread overview]
Message-ID: <1086042128.4690.16.camel@pegasus> (raw)
In-Reply-To: <1085937625.4462.5.camel@localhost.localdomain>

Hi David,

> This patch adds support to pand for writing a pidfile and cleaning up
> the client connection on exit. I'll go play with initscripts next...

I applied this patch with some small modifications. And btw you forgot
the diff for the man page ;)

>  static struct option main_lopts[] = {
>  	{ "help",     0, 0, 'h' },
>  	{ "listen",   0, 0, 's' },
> @@ -405,6 +481,8 @@
>  	{ "encrypt",  0, 0, 'E' },
>  	{ "master",   0, 0, 'M' },
>  	{ "cache",    0, 0, 'C' },
> +	{ "pidfile",  1, 0, 'P' },
> +	{ "autokill", 0, 0, 'a' },
>  	{ 0, 0, 0, 0 }
>  };

I don't like --autokill and -a option. I named it --autozap and used -z
as option.

> +		case 'P':
> +			pidfile = strdup(optarg);
> +			break;
> +
> +		case 'a':
> +			cleanup = 1;
> +			break;
> +

If you don't modify main_sopts, this won't work.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-05-31 22:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-11 19:29 [Bluez-devel] bluez-utils 2.7 default configuration Nicholas A. Preyss
2004-05-12 13:23 ` Marcel Holtmann
2004-05-12 14:18   ` David Woodhouse
2004-05-12 17:20     ` Marcel Holtmann
2004-05-12 17:25       ` David Woodhouse
2004-05-12 17:29         ` Marcel Holtmann
2004-05-12 17:33           ` David Woodhouse
2004-05-12 17:45             ` Marcel Holtmann
2004-05-12 17:56               ` David Woodhouse
2004-05-12 21:50                 ` Marcel Holtmann
2004-05-20  9:15               ` David Woodhouse
2004-05-20  9:20                 ` Marcel Holtmann
2004-05-20  9:28                   ` David Woodhouse
2004-05-20  9:42                     ` Marcel Holtmann
2004-05-20 22:04                       ` billy pucyutan
2004-05-30 17:20                 ` David Woodhouse
2004-05-31 22:22                   ` Marcel Holtmann [this message]
2004-05-31 22:43                     ` David Woodhouse

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=1086042128.4690.16.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=dwmw2@infradead.org \
    /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