2 /****** bsdsocket.library/getdtablesize *************************************
5 getdtablesize - get socket descriptor table size
12 long getdtablesize(void);
15 Return value of maximum number of open socket descriptors.
16 Larger socket descriptor table can be allocated with
17 SocketBaseTagList() call.
22 *****************************************************************************
26 /****** bsdsocket.library/syslog ********************************************
29 syslog, vsyslog - write message to AmiTCP/IP log.
34 vsyslog(level, format, ap)
37 void syslog(unsigned long level, char * format, ...);
39 void vsyslog(unsigned long level, char * format, ap);
42 Writes the message given as format string and arguments
43 (printf-style) both to the log file and to the console.
44 The message is prepended with the name of the calling
45 application, if the name is known by AmiTCP (the standard
46 autoinitiazer module in the net.lib passes the name of the
47 application to AmiTCP).
49 The level is selected from an ordered list:
51 LOG_EMERG A panic condition.
53 LOG_ALERT A condition that should be
54 corrected immediately, such as a
55 corrupted system database.
57 LOG_CRIT Critical conditions, such as hard
62 LOG_WARNING Warning messages.
64 LOG_NOTICE Conditions that are not error con-
65 ditions, but that may require spe-
68 LOG_INFO Informational messages.
70 LOG_DEBUG Messages that contain information
71 normally of use only when debugging
75 Level - indicates the type of the message. The levels
76 are defined in sys/syslog.h and listed above.
78 format - This is a printf-style format string.
80 arguments - as in printf().
82 ap - pointer to an array of arguments.
88 To log a message at priority LOG_INFO, it would make the
89 following call to syslog:
91 syslog(LOG_INFO, "Connection from host %s",
95 In contrast to the previous releases of the AmiTCP/IP, the
96 integer arguments are expected to be 32 bits wide, thus
97 eliminating the need to specify the 'l' size modifier for the
100 This function is callable from interrupts.
103 Because there is a limited number of internal messages used
104 by the logging system, some log messages may get lost if a
105 high priority task or interrupt handler sends many messages
106 in succession. If this happens, the next log message tells
110 net.lib/syslog for syslog utility functions (openlog(),
111 closelog() and setlogmask()),
112 C-library printf() documentation
114 *****************************************************************************