linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Harald Hoyer <harald@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: selinux
Date: Tue, 06 Apr 2004 15:15:12 +0000	[thread overview]
Message-ID: <4072C980.4080907@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 133 bytes --]

In extras there is udev_selinux. From where is this supposed to be called?

Attached is a totally untested patch to make it compile.

[-- Attachment #2: udev-024-selinux.patch --]
[-- Type: text/x-patch, Size: 1183 bytes --]

--- udev-024/extras/selinux/Makefile.sel	2004-04-05 17:59:22.640630568 +0200
+++ udev-024/extras/selinux/Makefile	2004-04-05 17:59:48.421711248 +0200
@@ -54,6 +54,7 @@
 
 
 install: all
+	$(INSTALL_PROGRAM) -D $(PROG) $(DESTDIR)$(sbindir)/$(PROG)
 
 uninstall: 
 
--- udev-024/extras/selinux/udev_selinux.c.sel	2004-04-03 00:47:28.000000000 +0200
+++ udev-024/extras/selinux/udev_selinux.c	2004-04-05 17:59:05.962166080 +0200
@@ -12,17 +12,32 @@
 
 #ifdef LOG
 unsigned char logname[LOGNAME_SIZE];
-void log_message(int level, const char *format, ...)
+static int debug;
+void log_message (int level, const char *format, ...)
 {
-	va_list args;
+	va_list	args;
 
-	if (!udev_log)
+	if (!debug && level == LOG_DEBUG)
 		return;
 
-	va_start(args, format);
-	vsyslog(level, format, args);
-	va_end(args);
+	va_start (args, format);
+	{
+		static int logging_init = 0;
+		if (!logging_init) {
+			/*
+			 * klibc does not have LOG_PID.
+			 */
+			snprintf(logname, 32, "udev_selinux[%d]", getpid());
+			openlog (logname, 0, LOG_DAEMON);
+			logging_init = 1;
+		}
+
+		vsyslog(level, format, args);
+	}
+	va_end (args);
+	return;
 }
+
 #endif
 
 void selinux_add_node(char *filename)

                 reply	other threads:[~2004-04-06 15:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4072C980.4080907@redhat.com \
    --to=harald@redhat.com \
    --cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).