Re: Why are we managing seusers file via libsemanage?

[Ivan Gyurdiev <ivg2@cornell.edu>]

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


> Ok well the seusers file should indicate that it is machine generated 
> and should not be edited then, or can it be eliminated all together.  
> Users will edit this file...
Patch attached - please also add the  header into the initial seusers 
file that gets installed, and into file_contexts.template in the policy.




[-- Attachment #2: libsemanage.autogen_header.diff --]
[-- Type: text/x-patch, Size: 754 bytes --]

diff -Naurp --exclude-from excludes old/libsemanage/src/database_file.c new/libsemanage/src/database_file.c
--- old/libsemanage/src/database_file.c	2006-01-17 09:11:06.000000000 -0700
+++ new/libsemanage/src/database_file.c	2006-01-17 11:26:15.000000000 -0700
@@ -159,6 +159,14 @@ static int dbase_file_flush(
 	}
 	__fsetlocking(str, FSETLOCKING_BYCALLER);
 
+	if (fprintf(str, "# This file is auto-generated by libsemanage\n"
+	                   "# Please use the semanage command to make "
+	                   "changes\n\n") < 0) {
+
+		ERR(handle, "could not write file header for %s", fname);
+		goto err;
+	}
+
 	for (ptr = dbase->llist.cache_tail; ptr != NULL; ptr = ptr->prev) {
 		if (rftable->print(handle, ptr->data, str) < 0)
 			goto err;