summaryrefslogtreecommitdiffstats
path: root/doc/new_chapters/eventlog.t
blob: 2c9459420133530d38a3c5053d34fac8d4d4ea60 (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
@c
@c  COPYRIGHT (c) 1988-1998.
@c  On-Line Applications Research Corporation (OAR).
@c  All rights reserved. 
@c
@c  $Id$
@c

@chapter Event Logging Manager

@section Introduction

The event logging manager provides a portable method for logging
system and application events and subsequent processing of those
events.  The capabilities in this manager were defined in the POSIX
1003.1h/D3 proposed standard titled @b{Services for Reliable,
Available, and Serviceable Systems}.

The directives provided by the event logging manager are:

@itemize @bullet
@item @code{log_write} - Write to the Log
@item @code{log_open} - Open a log file
@item @code{log_read} - Read from the system Log
@item @code{log_notify} - Notify Process of writes to the system log
@item @code{log_close} - Close log descriptor
@item @code{log_seek} - Reposition log file offset
@item @code{log_severity_before} - Compare event record severities
@item @code{log_facilityemptyset} - Manipulate log facility sets
@item @code{log_facilityfillset} - Manipulate log facility sets
@item @code{log_facilityaddset} - Manipulate log facility sets
@item @code{log_facilitydelset} - Manipulate log facility sets
@item @code{log_facilityismember} - Manipulate log facility sets
@end itemize

@section Background

@subsection Log Files and Events

System log

Non-system logs

Events, facility, severity

@subsection Queries

@section Operations

@subsection Creating and Writing a non-System Log

Discuss creating and writing to a non-system log.

@example
  log_create
  log_write loop
@end example

@subsection Reading a Log

Discuss opening and reading from a log.

@example
  build a query
  log_open
  log_read loop
@end example

@section Directives

This section details the event logging manager's directives.
A subsection is dedicated to each of this manager's directives
and describes the calling sequence, related constants, usage,
and status codes.

@page
@subsection log_write - Write to the Log

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_write(
  const log_facility_t  facility,
  const int             event_id,
  const log_severity_t  severity,
  const void           *buf,
  const size_t          len
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EINVAL
The facility argument is not a valid log_facility.

@item EINVAL
The severity argument exceeds @code{LOG_SEVERITY_MAX}

@item EINVAL
The len argument exceeds @code{LOG_ENTRY_MAXLEN}

@item ENOSPC
The log file has run out of space on the device.

@item EPERM
The caller does not have appropriate permission for writing to
the given facility.

@item EIO
An I/O error occurred in writing to the system event log.

@end table

@subheading DESCRIPTION:

The @code{log_write} function writes an event record, consisting 
of event attributes, and the data identified by the @code{buf} 
argument, to the system log.  The @code{len} argument specifies
the length in bytes of the buffer pointed to by @code{buf}.  The
@code{len} argument shall specify the value of the event record
length attribute.  The value of @code{len} shall be less than or 
equal to @code{LOG_ENTRY_MAXLEN} or the @code{log_write} shall fail.

The @code{event_id} argument identifies the type of event record
being written.  The @code{event_id} argument shall specify the value
of the event ID attribute of the event record.

The argument @code{facility} indicates the facility from which the
event type is drawn.  The @code{facility} argument shall specify the
value of the event record facility attribute.  The value of the
@code{facility} argument shall be a valid log facility or the 
@code{log_write} function shall fail.

The @code{severity} argument indicates the severity level of the
event record.  The @code{severity} argument shall specify the value
of the event record severity attribute.  The value of the 
@code{severity} argument shall be less than or equal to 
@code{LOG_SEVERITY_MAX} or the @code{log_write} function shall fail.  

The effective_UID of the calling process shall specify the event
record UID attribute.  The effective-GID of the calling process 
shall specify the event record GID attribute.  The process ID
of the calling process shall specify the event record process ID
attribute.  The process group ID of the calling process shall
specify the event record process group ID attribute.  The current
value of the system clock shall specify the event record timestamp
attribute.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_open - Open a log file

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_open(
  const logd_t         *logdes,
  const char           *path,
  const log_query_t    *query
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EACCES
Search permission is denied on a component of the path prefix,
or the log file exists and read permission is denied.

@item  EINTR
A signal interrupted the call to log_open().

@item EINVAL
The log_facility field of the query argument is not a valid 
facility set.

@item EINVAL
The log_severity field of the query argument exceeds 
@code{LOG_SEVERITY_MAX}.

@item EINVAL
The path argument referred to a file that was not a log file.

@item EMFILE
Too many log file descriptors are currently in use by this
process.

@item ENAMETOOLONG
The length of the path string exceeds @code{PATH_MAX}, or a pathname
component is longer than @code{NAME_MAX} while @code{_POSIX_NO_TRUNC} is
in effect.

@item ENFILE
Too many files are currently open in the system.

@item ENOENT
The file specified by the path argument does not exist.

@item ENOTDIR
A component of the path prefix is not a directory.

@end table

@subheading DESCRIPTION:

The @code{log_open} function establishes the connection between a 
log file and a log file descriptor.  It creates an open log file 
description that refers to a log file and a log file descriptor that
refers to that open log file description.  The log file descriptor is
used by other log functions to refer to that log file.  The @code{path}
argument points to a pathname naming a log file.  A @code{path}
argument of NULL specifies the current system log file.  

The @code{query} argument points to a log query specification that
restricts log operations using the returned log file descriptor to 
to event records from the log file which match the query.  The 
predicate which determines the success of the match operation is the
logical AND of the individual comparison predicates for each member
of the log query specification.  The query attribute of the open file
description is set to filter as specified by the @code{query} argument.
If the value of the query argument is not NULL, the value of the 
@code{log_facility} member of the @code{query} specification shall be
a set of valid log facilities or the @code{log_open} shall fail.  If
the value of the @code{query} argument is not NULL, the value of the
@code{log_severity} member of the @code{query} specification shall be
less than or equal to @code{LOG_SEVERITY_MAX} or the @code{log_open}
shall fail.  If the value of the @code{query} argument is NULL, no
query filter shall be applied. 

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_read - Read from the system Log

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_read(
  const logd_t logdes,
  struct log_entry *entry,
  void             *log_buf,
  const size_t      log_len,
  const size_t     *log_sizeread
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EBADF
The logdes argument is not a valid log file descriptor.

@item EBUSY
No data available.  The open log file descriptor references
the current system log.  and there are no unread event records
remaining.

@item EINTR
A signal interrupted the call to log_read().

@item EIO
An I/O error occurred in reading from the event log.

@end table

@subheading DESCRIPTION:

The @code{log_read} function shall attempt to read the @code{log_entry}
structure and @code{log_len} bytes of data from the next event record 
of the log file associated with the open log file descriptor @code{logdes},
placing the @code{log_entry} structure into the buffer pointed to by
@code{entry}, and the data into the buffer pointed to by @code{log_buf}.
The log record ID of the returned event record shall be stored in the 
@code{log_recid} member of the @code{log_entry} structure for the event
record.

If the query attribute of the open log file description associated with
the @code{logdes} is set, the event record read shall match that query.
If the @code{entry} argument is not NULL it will point to a @code{log_entry}
structure which shall be filled with the creation information for this log
entry.  If the argument @code{log_buf} is not NULL the data written with the
log entry will be placed in the buffer.  The size of the buffer is specified
by the argument @code{log_len}.

If the @code{log_read} is successful the call shall store the actual length
of the data associated with the event record into the location specified by
@code{log_sizeread}.  This number may be smaller or greater than 
@code{log_len}.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_notify - Notify Process of writes to the system log.

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_notify(
  const logd_t           logdes,
  const struct sigevent *notification
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EBADF
The logdes argument is not a valid log file descriptor.

@item EINVAL
The notification argument specifies an invalid signal.

@item EINVAL
The process has requested a notify on a log that will not be
written to.

@item ENOSY
The function log_notify() is not supported by this implementation.

@end table

@subheading DESCRIPTION:

If the argument @code{notification} is not NULL this function registers 
the calling process to be notified of event records received by the system 
log, which match the query parameters associated with the open log descriptor
specified by @code{logdes}.  The notification specified by the 
@code{notification} argument shall be sent to the process when an event 
record received by the system log is matched by the query attribute of the 
open log file description associated with the @code{logdes} log file 
descriptor.  If the calling process has already registered a notification
for the @code{logdes} log file descriptor, the new notification shall 
replace the existing notification registration.

If the @code{notification} argument is NULL and the calling process is 
currently registered to be notified for the @code{logdes} log file
descriptor, the existing registration shall be removed.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_close - Close log descriptor

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_close(
  const logd_t   logdes
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EBADF
The logdes argument is not a valid log file descriptor.

@end table

@subheading DESCRIPTION:

The @code{log_close} function deallocates the open log file descriptor 
indicated by @code{log_des}.

When all log file descriptors associated with an open log file description
have been closed, the open log file description shall be freed.

If the link count of the log file is zero, when all log file descriptors
have been closed, the space occupied by the log file shall be freed and the
log file shall no longer be accessible.

If the process has successfully registered a notification request for the 
log file descriptor, the registration shall be removed. 

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_seek - Reposition log file offset

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_seek(
  const logd_t    logdes,
  log_recid_t     log_recid
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EBADF
The logdes argument is not a valid log file descriptor.

@item EINTR
The log_seek() function was interrupted by a signal.

@item EINVAL
The log_recid argument is not a valid record id.

@end table

@subheading DESCRIPTION:

The @code{log_seek} function shall set the log file offset of the open 
log description associated with the @code{logdes} log file descriptor 
to the event record in the log file identified by @code{log_recid}.  
The @code{log_recid} argument is either the record id of a valid event
record or one of the following values, as defined in the header <evlog.h>:

@table @b
@item LOG_SEEK_START
Set log file position to point at the first event
record in the log file

@item LOG_SEEK_END
Set log file position to point after the last event 
record in the log file

@end table

If the @code{log_seek} function is interrupted, the state of the open log
file description associated with @code{logdes} is unspecified.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_severity_before - Compare event record severities

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_severity_before(
  log_severity_t  s1,
  log_severity_t  s2
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EINVAL 
The value of either s1 or s2 exceeds @code{LOG_SEVERITY_MAX}.

@end table

@subheading DESCRIPTION:

The @code{log_severity_before} function shall compare the severity order
of the @code{s1} and @code{s2} arguments.  Severity values ordered 
according to this function shall be according to decreasing severity.

If @code{s1} is ordered before or is equal to @code{s2} then the ordering
predicate shall return 1, otherwise the predicate shall return 0.  If 
either @code{s1} or @code{s2} specify invalid severity values, the return
value of @code{log_severity_before} is unspecified.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_facilityemptyset - Manipulate log facility sets

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_facilityemptyset(
  log_facility_set_t  *set
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EINVAL
The facilityno argument is not a valid facility.

@end table

@subheading DESCRIPTION:

The facilitysetops primitives manipulate sets of facilities.  They 
operate on data objects addressable by the application.

The @code{log_facilityemptyset} function initializes the facility
set pointed to by the argument @code{set}, such that all facilities
are included.

Applications shall call either @code{log_facilityemptyset} or 
@code{log_facilityfillset} at least once for each object of type
@code{log_facilityset_t} prior to any other use of that object.  If
such an object is not initialized in this way, but is nonetheless 
supplied as an argument  to any of the @code{log_facilityaddset}, 
@code{logfacilitydelset}, @code{log_facilityismember} or 
@code{log_open} functions, the results are undefined.

The @code{log_facilityaddset} and @code{log_facilitydelset} functions
respectively add or delete the individual facility specified by the
value of the argument @code{facilityno} to or from the facility set
pointed to by the argument @code{set}

The @code{log_facilityismember} function tests whether the facility
specified by the value of the argument @code{facilityno} is a member
of the set pointed to by the argument @code{set}.  Upon successful
completion, the @code{log_facilityismember} function either returns
a value of one to the location specified by @code{member} if the 
specified facility is a member of the specified set or returns a 
value of zero to the location specified by @code{member} if the
specified facility is not a member of the specified set.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_facilityfillset - Manipulate log facility sets

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_facilityfillset(
  log_facility_set_t  *set
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EINVAL
The facilityno argument is not a valid facility.

@end table

@subheading DESCRIPTION:

The facilitysetops primitives manipulate sets of facilities.  They 
operate on data objects addressable by the application.

The @code{log_facilityemptyset} function initializes the facility
set pointed to by the argument @code{set}, such that all facilities
are included.

Applications shall call either @code{log_facilityemptyset} or 
@code{log_facilityfillset} at least once for each object of type
@code{log_facilityset_t} prior to any other use of that object.  If
such an object is not initialized in this way, but is nonetheless 
supplied as an argument  to any of the @code{log_facilityaddset}, 
@code{logfacilitydelset}, @code{log_facilityismember} or 
@code{log_open} functions, the results are undefined.

The @code{log_facilityaddset} and @code{log_facilitydelset} functions
respectively add or delete the individual facility specified by the
value of the argument @code{facilityno} to or from the facility set
pointed to by the argument @code{set}

The @code{log_facilityismember} function tests whether the facility
specified by the value of the argument @code{facilityno} is a member
of the set pointed to by the argument @code{set}.  Upon successful
completion, the @code{log_facilityismember} function either returns
a value of one to the location specified by @code{member} if the 
specified facility is a member of the specified set or returns a 
value of zero to the location specified by @code{member} if the
specified facility is not a member of the specified set.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_facilityaddset - Manipulate log facility sets

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_facilityaddset(
  log_facility_set_t  *set,
  log_facility_t      facilityno
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EINVAL
The facilityno argument is not a valid facility.

@end table

@subheading DESCRIPTION:

The facilitysetops primitives manipulate sets of facilities.  They 
operate on data objects addressable by the application.

The @code{log_facilityemptyset} function initializes the facility
set pointed to by the argument @code{set}, such that all facilities
are included.

Applications shall call either @code{log_facilityemptyset} or 
@code{log_facilityfillset} at least once for each object of type
@code{log_facilityset_t} prior to any other use of that object.  If
such an object is not initialized in this way, but is nonetheless 
supplied as an argument  to any of the @code{log_facilityaddset}, 
@code{logfacilitydelset}, @code{log_facilityismember} or 
@code{log_open} functions, the results are undefined.

The @code{log_facilityaddset} and @code{log_facilitydelset} functions
respectively add or delete the individual facility specified by the
value of the argument @code{facilityno} to or from the facility set
pointed to by the argument @code{set}

The @code{log_facilityismember} function tests whether the facility
specified by the value of the argument @code{facilityno} is a member
of the set pointed to by the argument @code{set}.  Upon successful
completion, the @code{log_facilityismember} function either returns
a value of one to the location specified by @code{member} if the 
specified facility is a member of the specified set or returns a 
value of zero to the location specified by @code{member} if the
specified facility is not a member of the specified set.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_facilitydelset - Manipulate log facility sets

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_facilitydelset(
  log_facility_set_t  *set,
  log_facility_t      facilityno
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EINVAL
The facilityno argument is not a valid facility.

@end table

@subheading DESCRIPTION:

The facilitysetops primitives manipulate sets of facilities.  They 
operate on data objects addressable by the application.

The @code{log_facilityemptyset} function initializes the facility
set pointed to by the argument @code{set}, such that all facilities
are included.

Applications shall call either @code{log_facilityemptyset} or 
@code{log_facilityfillset} at least once for each object of type
@code{log_facilityset_t} prior to any other use of that object.  If
such an object is not initialized in this way, but is nonetheless 
supplied as an argument  to any of the @code{log_facilityaddset}, 
@code{logfacilitydelset}, @code{log_facilityismember} or 
@code{log_open} functions, the results are undefined.

The @code{log_facilityaddset} and @code{log_facilitydelset} functions
respectively add or delete the individual facility specified by the
value of the argument @code{facilityno} to or from the facility set
pointed to by the argument @code{set}

The @code{log_facilityismember} function tests whether the facility
specified by the value of the argument @code{facilityno} is a member
of the set pointed to by the argument @code{set}.  Upon successful
completion, the @code{log_facilityismember} function either returns
a value of one to the location specified by @code{member} if the 
specified facility is a member of the specified set or returns a 
value of zero to the location specified by @code{member} if the
specified facility is not a member of the specified set.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_facilityismember - Manipulate log facility sets

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_facilityismember(
  const log_facility_set_t *set,
  log_facility_t            facilityno,
  const int                *member
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EINVAL
The facilityno argument is not a valid facility.

@end table

@subheading DESCRIPTION:

The facilitysetops primitives manipulate sets of facilities.  They 
operate on data objects addressable by the application.

The @code{log_facilityemptyset} function initializes the facility
set pointed to by the argument @code{set}, such that all facilities
are included.

Applications shall call either @code{log_facilityemptyset} or 
@code{log_facilityfillset} at least once for each object of type
@code{log_facilityset_t} prior to any other use of that object.  If
such an object is not initialized in this way, but is nonetheless 
supplied as an argument  to any of the @code{log_facilityaddset}, 
@code{logfacilitydelset}, @code{log_facilityismember} or 
@code{log_open} functions, the results are undefined.

The @code{log_facilityaddset} and @code{log_facilitydelset} functions
respectively add or delete the individual facility specified by the
value of the argument @code{facilityno} to or from the facility set
pointed to by the argument @code{set}

The @code{log_facilityismember} function tests whether the facility
specified by the value of the argument @code{facilityno} is a member
of the set pointed to by the argument @code{set}.  Upon successful
completion, the @code{log_facilityismember} function either returns
a value of one to the location specified by @code{member} if the 
specified facility is a member of the specified set or returns a 
value of zero to the location specified by @code{member} if the
specified facility is not a member of the specified set.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_create - Creates a log file

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_create(
  logd_t       *ld,
  const char   *path,
);
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item ENOMEM
The is ????????????

@end table

@subheading DESCRIPTION:

This function dynamically allocates memory for the @code{ld}, associates 
a directory path to the @code{Ld}, and provides access permissions to the
@code{ld}.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.

@page
@subsection log_sys_create - Creates a system log file

@subheading CALLING SEQUENCE:

@ifset is-C
@example
int log_sys_create();
@end example
@end ifset

@ifset is-Ada
@end ifset

@subheading STATUS CODES:

@table @b
@item EEXIST
The directory path to the system log already exist.

@end table

@subheading DESCRIPTION:

This function will create a predefined system log directory path and
system log file if they do not already exist.

@subheading NOTES:

The @code{_POSIX_LOGGING} feature flag is defined to indicate
this service is available.