Unlike
.IR race ,
which causes both readers and
-writers of internal objects to be regarded as MT-Unsafe, \" and AS-Unsafe,
+writers of internal objects to be regarded as MT-Unsafe,\" and AS-Unsafe,
this mark is applied to writers only.
-Writers remain \" equally
-MT-Unsafe \" and AS-Unsafe
+Writers remain\" equally
+MT-Unsafe\" and AS-Unsafe
to call,
but the then-mandatory constness of objects they
-modify enables readers to be regarded as MT-Safe \" and AS-Safe
+modify enables readers to be regarded as MT-Safe\" and AS-Safe
(as long as no other reasons for them to be unsafe remain),
since the lack of synchronization is not a problem when the
objects are effectively constant.
behave in ways that do not correspond to any of the locales active
during their execution, but an unpredictable mix thereof.
.IP
-We do not mark these functions as MT-Unsafe, \" or AS-Unsafe,
+We do not mark these functions as MT-Unsafe,\" or AS-Unsafe,
however,
because functions that modify the locale object are marked with
.I const:locale
or similar, without any guards to ensure
safety in the presence of concurrent modifications.
.IP
-We do not mark these functions as MT-Unsafe, \" or AS-Unsafe,
+We do not mark these functions as MT-Unsafe,\" or AS-Unsafe,
however,
because functions that modify the environment are all marked with
.I const:env
internal data structure without any guards to ensure
safety in the presence of concurrent modifications.
.IP
-We do not mark these functions as MT-Unsafe, \" or AS-Unsafe,
+We do not mark these functions as MT-Unsafe,\" or AS-Unsafe,
however,
because functions that modify this data structure are all marked with
.I const:sigintr
Examples include the following:
.IP * 3
The variables
-.BR LANG ", " LANGUAGE ", " NLSPATH ", " LOCPATH ", "
-.BR LC_ALL ", " LC_MESSAGES ", "
+.BR LANG ", " LANGUAGE ", " NLSPATH ", " LOCPATH ,
+.BR LC_ALL ", " LC_MESSAGES ,
and so on influence locale handling; see
.BR catopen (3),
.BR gettext (3),
.B AF_UNSPEC
when the source was unknown.
When the error originated from the network, all IP options
-.RB ( IP_OPTIONS ", " IP_TTL ", "
+.RB ( IP_OPTIONS ", " IP_TTL ,
etc.) enabled on the socket and contained in the
error packet are passed as control messages.
The payload of the packet causing the error is returned as normal payload.
cannot be caught, blocked, or ignored.
.PP
Up to and including Linux 2.2, the default behavior for
-.BR SIGSYS ", " SIGXCPU ", " SIGXFSZ ", "
+.BR SIGSYS ", " SIGXCPU ", " SIGXFSZ ,
and (on architectures other than SPARC and MIPS)
.B SIGBUS
was to terminate the process (without a core dump).