public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Georg Nikodym" <georgn@somanetworks.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: georgn@somanetworks.com, linux-kernel@vger.kernel.org,
	greg@wind.enjellic.com, sct@redhat.com,
	Linus Torvalds <torvalds@transmeta.com>,
	"Adam J. Richter" <adam@yggdrasil.com>
Subject: Re: linux-2.4.0-test11 and sysklogd-1.3-31
Date: Mon, 11 Dec 2000 20:53:16 -0500 (EST)	[thread overview]
Message-ID: <14901.34060.536976.829050@somanetworks.com> (raw)
In-Reply-To: <3586.976584600@kao2.melbourne.sgi.com>
In-Reply-To: <14901.31690.961664.201896@somanetworks.com> <3586.976584600@kao2.melbourne.sgi.com>

>>>>> "KO" == Keith Owens <kaos@ocs.com.au> writes:

 KO> Looks good, except that you need to keep the option flags for
 KO> backwards compatibility.  There are a *lot* of scripts out there
 KO> which invoke klogd with various options and they will fail with
 KO> this change.  It is OK to issue a warning message "klogd options
 KO> -[iIpkx] are no longer supported" as long as klogd continues to
 KO> run.  Otherwise you will get a lot of irate users complaining
 KO> that klogd is failing at boot time.

You're right.  Here's YAP:

diff -Nru a/src/sysklogd-1.3-31/klogd.c b/src/sysklogd-1.3-31/klogd.c
--- a/src/sysklogd-1.3-31/klogd.c	Mon Dec 11 20:50:49 2000
+++ b/src/sysklogd-1.3-31/klogd.c	Mon Dec 11 20:50:49 2000
@@ -763,7 +763,7 @@
 	chdir ("/");
 #endif
 	/* Parse the command-line. */
-	while ((ch = getopt(argc, argv, "c:df:nosv")) != EOF)
+	while ((ch = getopt(argc, argv, "c:df:nosviIk:px")) != EOF)
 		switch((char)ch)
 		{
 		    case 'c':		/* Set console message level. */
@@ -788,6 +788,20 @@
 		    case 'v':
 			printf("klogd %s-%s\n", VERSION, PATCHLEVEL);
 			exit (1);
+
+		    /* Obsolete options */
+		    case 'i':
+			/* FALLTHRU */
+		    case 'I':
+			/* FALLTHRU */
+		    case 'k':
+			/* FALLTHRU */
+		    case 'p':
+			/* FALLTHRU */
+		    case 'x':
+			fprintf(stderr,
+				"klogd: %c option is obsolete.  Ignoring\n", ch);
+			break;
 		}
 
 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-12  2:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06 22:24 linux-2.4.0-test11 and sysklogd-1.3-31 Georg Nikodym
2000-12-06 23:46 ` Keith Owens
2000-12-07 17:36   ` Georg Nikodym
2000-12-07 22:51     ` Keith Owens
2000-12-08 16:30       ` Georg Nikodym
2000-12-08 22:16         ` Keith Owens
2000-12-12  1:13           ` Georg Nikodym
2000-12-12  1:29             ` Georg Nikodym
2000-12-12  1:30             ` Keith Owens
2000-12-12  1:53               ` Georg Nikodym [this message]
2000-12-12  3:57                 ` Peter Samuelson

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=14901.34060.536976.829050@somanetworks.com \
    --to=georgn@somanetworks.com \
    --cc=adam@yggdrasil.com \
    --cc=greg@wind.enjellic.com \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sct@redhat.com \
    --cc=torvalds@transmeta.com \
    /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