… | |
… | |
403 | will not restart syscalls (that includes Async::Interrupt and AnyEvent's |
403 | will not restart syscalls (that includes Async::Interrupt and AnyEvent's |
404 | pure perl implementation). |
404 | pure perl implementation). |
405 | |
405 | |
406 | Safe/Unsafe Signals |
406 | Safe/Unsafe Signals |
407 | Perl signals can be either "safe" (synchronous to opcode handling) or |
407 | Perl signals can be either "safe" (synchronous to opcode handling) or |
408 | "unsafe" (asynchronous) - the former might get delayed indefinitely, the |
408 | "unsafe" (asynchronous) - the former might delay signal delivery |
409 | latter might corrupt your memory. |
409 | indefinitely, the latter might corrupt your memory. |
410 | |
410 | |
411 | AnyEvent signal handlers are, in addition, synchronous to the event |
411 | AnyEvent signal handlers are, in addition, synchronous to the event |
412 | loop, i.e. they will not interrupt your running perl program but will |
412 | loop, i.e. they will not interrupt your running perl program but will |
413 | only be called as part of the normal event handling (just like timer, |
413 | only be called as part of the normal event handling (just like timer, |
414 | I/O etc. callbacks, too). |
414 | I/O etc. callbacks, too). |
… | |
… | |
416 | Signal Races, Delays and Workarounds |
416 | Signal Races, Delays and Workarounds |
417 | Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching |
417 | Many event loops (e.g. Glib, Tk, Qt, IO::Async) do not support attaching |
418 | callbacks to signals in a generic way, which is a pity, as you cannot do |
418 | callbacks to signals in a generic way, which is a pity, as you cannot do |
419 | race-free signal handling in perl, requiring C libraries for this. |
419 | race-free signal handling in perl, requiring C libraries for this. |
420 | AnyEvent will try to do its best, which means in some cases, signals |
420 | AnyEvent will try to do its best, which means in some cases, signals |
421 | will be delayed. The maximum time a signal might be delayed is specified |
421 | will be delayed. The maximum time a signal might be delayed is 10 |
422 | in $AnyEvent::MAX_SIGNAL_LATENCY (default: 10 seconds). This variable |
422 | seconds by default, but can be overriden via |
423 | can be changed only before the first signal watcher is created, and |
423 | $ENV{PERL_ANYEVENT_MAX_SIGNAL_LATENCY} or $AnyEvent::MAX_SIGNAL_LATENCY |
424 | should be left alone otherwise. This variable determines how often |
424 | - see the Ö<ENVIRONMENT VARIABLES> section for details. |
425 | AnyEvent polls for signals (in case a wake-up was missed). Higher values |
|
|
426 | will cause fewer spurious wake-ups, which is better for power and CPU |
|
|
427 | saving. |
|
|
428 | |
425 | |
429 | All these problems can be avoided by installing the optional |
426 | All these problems can be avoided by installing the optional |
430 | Async::Interrupt module, which works with most event loops. It will not |
427 | Async::Interrupt module, which works with most event loops. It will not |
431 | work with inherently broken event loops such as Event or Event::Lib (and |
428 | work with inherently broken event loops such as Event or Event::Lib (and |
432 | not with POE currently, as POE does its own workaround with one-second |
|
|
433 | latency). For those, you just have to suffer the delays. |
429 | not with POE currently). For those, you just have to suffer the delays. |
434 | |
430 | |
435 | CHILD PROCESS WATCHERS |
431 | CHILD PROCESS WATCHERS |
436 | $w = AnyEvent->child (pid => <process id>, cb => <callback>); |
432 | $w = AnyEvent->child (pid => <process id>, cb => <callback>); |
437 | |
433 | |
438 | You can also watch for a child process exit and catch its exit status. |
434 | You can also watch for a child process exit and catch its exit status. |
… | |
… | |
839 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
835 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
840 | AnyEvent::Impl::POE based on POE, very slow, some limitations. |
836 | AnyEvent::Impl::POE based on POE, very slow, some limitations. |
841 | AnyEvent::Impl::Irssi used when running within irssi. |
837 | AnyEvent::Impl::Irssi used when running within irssi. |
842 | AnyEvent::Impl::IOAsync based on IO::Async. |
838 | AnyEvent::Impl::IOAsync based on IO::Async. |
843 | AnyEvent::Impl::Cocoa based on Cocoa::EventLoop. |
839 | AnyEvent::Impl::Cocoa based on Cocoa::EventLoop. |
844 | AnyEvent::Impl::FLTK2 based on FLTK (fltk 2 binding). |
840 | AnyEvent::Impl::FLTK based on FLTK (fltk 2 binding). |
845 | |
841 | |
846 | Backends with special needs. |
842 | Backends with special needs. |
847 | Qt requires the Qt::Application to be instantiated first, but will |
843 | Qt requires the Qt::Application to be instantiated first, but will |
848 | otherwise be picked up automatically. As long as the main program |
844 | otherwise be picked up automatically. As long as the main program |
849 | instantiates the application before any AnyEvent watchers are |
845 | instantiates the application before any AnyEvent watchers are |
… | |
… | |
1005 | if $some_error_condition; |
1001 | if $some_error_condition; |
1006 | |
1002 | |
1007 | AnyEvent::log $level, $msg[, @args] |
1003 | AnyEvent::log $level, $msg[, @args] |
1008 | Log the given $msg at the given $level. |
1004 | Log the given $msg at the given $level. |
1009 | |
1005 | |
|
|
1006 | If AnyEvent::Log is not loaded then this function makes a simple |
|
|
1007 | test to see whether the message will be logged. If the test succeeds |
1010 | Loads AnyEvent::Log on first use and calls "AnyEvent::Log::log" - |
1008 | it will load AnyEvent::Log and call "AnyEvent::Log::log" - |
1011 | consequently, look at the AnyEvent::Log documentation for details. |
1009 | consequently, look at the AnyEvent::Log documentation for details. |
|
|
1010 | |
|
|
1011 | If the test fails it will simply return. Right now this happens when |
|
|
1012 | a numerical loglevel is used and it is larger than the level |
|
|
1013 | specified via $ENV{PERL_ANYEVENT_VERBOSE}. |
1012 | |
1014 | |
1013 | If you want to sprinkle loads of logging calls around your code, |
1015 | If you want to sprinkle loads of logging calls around your code, |
1014 | consider creating a logger callback with the "AnyEvent::Log::logger" |
1016 | consider creating a logger callback with the "AnyEvent::Log::logger" |
1015 | function. |
1017 | function, which can reduce typing, codesize and can reduce the |
|
|
1018 | logging overhead enourmously. |
1016 | |
1019 | |
1017 | WHAT TO DO IN A MODULE |
1020 | WHAT TO DO IN A MODULE |
1018 | As a module author, you should "use AnyEvent" and call AnyEvent methods |
1021 | As a module author, you should "use AnyEvent" and call AnyEvent methods |
1019 | freely, but you should not load a specific event module or rely on it. |
1022 | freely, but you should not load a specific event module or rely on it. |
1020 | |
1023 | |
… | |
… | |
1103 | AnyEvent::IGS, AnyEvent::FCP |
1106 | AnyEvent::IGS, AnyEvent::FCP |
1104 | Implement event-based interfaces to the protocols of the same name |
1107 | Implement event-based interfaces to the protocols of the same name |
1105 | (for the curious, IGS is the International Go Server and FCP is the |
1108 | (for the curious, IGS is the International Go Server and FCP is the |
1106 | Freenet Client Protocol). |
1109 | Freenet Client Protocol). |
1107 | |
1110 | |
1108 | AnyEvent::Handle::UDP |
|
|
1109 | Here be danger! |
|
|
1110 | |
|
|
1111 | As Pauli would put it, "Not only is it not right, it's not even |
|
|
1112 | wrong!" - there are so many things wrong with AnyEvent::Handle::UDP, |
|
|
1113 | most notably its use of a stream-based API with a protocol that |
|
|
1114 | isn't streamable, that the only way to improve it is to delete it. |
|
|
1115 | |
|
|
1116 | It features data corruption (but typically only under load) and |
|
|
1117 | general confusion. On top, the author is not only clueless about UDP |
|
|
1118 | but also fact-resistant - some gems of his understanding: "connect |
|
|
1119 | doesn't work with UDP", "UDP packets are not IP packets", "UDP only |
|
|
1120 | has datagrams, not packets", "I don't need to implement proper error |
|
|
1121 | checking as UDP doesn't support error checking" and so on - he |
|
|
1122 | doesn't even understand what's wrong with his module when it is |
|
|
1123 | explained to him. |
|
|
1124 | |
|
|
1125 | AnyEvent::DBI |
|
|
1126 | Executes DBI requests asynchronously in a proxy process for you, |
|
|
1127 | notifying you in an event-based way when the operation is finished. |
|
|
1128 | |
|
|
1129 | AnyEvent::AIO |
1111 | AnyEvent::AIO |
1130 | Truly asynchronous (as opposed to non-blocking) I/O, should be in |
1112 | Truly asynchronous (as opposed to non-blocking) I/O, should be in |
1131 | the toolbox of every event programmer. AnyEvent::AIO transparently |
1113 | the toolbox of every event programmer. AnyEvent::AIO transparently |
1132 | fuses IO::AIO and AnyEvent together, giving AnyEvent access to |
1114 | fuses IO::AIO and AnyEvent together, giving AnyEvent access to |
1133 | event-based file I/O, and much more. |
1115 | event-based file I/O, and much more. |
1134 | |
1116 | |
|
|
1117 | AnyEvent::Filesys::Notify |
|
|
1118 | AnyEvent is good for non-blocking stuff, but it can't detect file or |
|
|
1119 | path changes (e.g. "watch this directory for new files", "watch this |
|
|
1120 | file for changes"). The AnyEvent::Filesys::Notify module promises to |
|
|
1121 | do just that in a portbale fashion, supporting inotify on GNU/Linux |
|
|
1122 | and some weird, without doubt broken, stuff on OS X to monitor |
|
|
1123 | files. It can fall back to blocking scans at regular intervals |
|
|
1124 | transparently on other platforms, so it's about as portable as it |
|
|
1125 | gets. |
|
|
1126 | |
|
|
1127 | (I haven't used it myself, but I haven't heard anybody complaining |
|
|
1128 | about it yet). |
|
|
1129 | |
|
|
1130 | AnyEvent::DBI |
|
|
1131 | Executes DBI requests asynchronously in a proxy process for you, |
|
|
1132 | notifying you in an event-based way when the operation is finished. |
|
|
1133 | |
1135 | AnyEvent::HTTPD |
1134 | AnyEvent::HTTPD |
1136 | A simple embedded webserver. |
1135 | A simple embedded webserver. |
1137 | |
1136 | |
1138 | AnyEvent::FastPing |
1137 | AnyEvent::FastPing |
1139 | The fastest ping in the west. |
1138 | The fastest ping in the west. |
1140 | |
1139 | |
1141 | Coro |
1140 | Coro |
1142 | Has special support for AnyEvent via Coro::AnyEvent. |
1141 | Has special support for AnyEvent via Coro::AnyEvent, which allows |
|
|
1142 | you to simply invert the flow control - don't call us, we will call |
|
|
1143 | you: |
|
|
1144 | |
|
|
1145 | async { |
|
|
1146 | Coro::AnyEvent::sleep 5; # creates a 5s timer and waits for it |
|
|
1147 | print "5 seconds later!\n"; |
|
|
1148 | |
|
|
1149 | Coro::AnyEvent::readable *STDIN; # uses an I/O watcher |
|
|
1150 | my $line = <STDIN>; # works for ttys |
|
|
1151 | |
|
|
1152 | AnyEvent::HTTP::http_get "url", Coro::rouse_cb; |
|
|
1153 | my ($body, $hdr) = Coro::rouse_wait; |
|
|
1154 | }; |
1143 | |
1155 | |
1144 | SIMPLIFIED AE API |
1156 | SIMPLIFIED AE API |
1145 | Starting with version 5.0, AnyEvent officially supports a second, much |
1157 | Starting with version 5.0, AnyEvent officially supports a second, much |
1146 | simpler, API that is designed to reduce the calling, typing and memory |
1158 | simpler, API that is designed to reduce the calling, typing and memory |
1147 | overhead by using function call syntax and a fixed number of parameters. |
1159 | overhead by using function call syntax and a fixed number of parameters. |
… | |
… | |
1163 | The pure perl event loop simply re-throws the exception (usually within |
1175 | The pure perl event loop simply re-throws the exception (usually within |
1164 | "condvar->recv"), the Event and EV modules call "$Event/EV::DIED->()", |
1176 | "condvar->recv"), the Event and EV modules call "$Event/EV::DIED->()", |
1165 | Glib uses "install_exception_handler" and so on. |
1177 | Glib uses "install_exception_handler" and so on. |
1166 | |
1178 | |
1167 | ENVIRONMENT VARIABLES |
1179 | ENVIRONMENT VARIABLES |
1168 | The following environment variables are used by this module or its |
1180 | AnyEvent supports a number of environment variables that tune the |
1169 | submodules. |
1181 | runtime behaviour. They are usually evaluated when AnyEvent is loaded, |
|
|
1182 | initialised, or a submodule that uses them is loaded. Many of them also |
|
|
1183 | cause AnyEvent to load additional modules - for example, |
|
|
1184 | "PERL_ANYEVENT_DEBUG_WRAP" causes the AnyEvent::Debug module to be |
|
|
1185 | loaded. |
1170 | |
1186 | |
1171 | Note that AnyEvent will remove *all* environment variables starting with |
1187 | All the environment variables documented here start with |
1172 | "PERL_ANYEVENT_" from %ENV when it is loaded while taint mode is |
1188 | "PERL_ANYEVENT_", which is what AnyEvent considers its own namespace. |
1173 | enabled. |
1189 | Other modules are encouraged (but by no means required) to use |
|
|
1190 | "PERL_ANYEVENT_SUBMODULE" if they have registered the |
|
|
1191 | AnyEvent::Submodule namespace on CPAN, for any submodule. For example, |
|
|
1192 | AnyEvent::HTTP could be expected to use "PERL_ANYEVENT_HTTP_PROXY" (it |
|
|
1193 | should not access env variables starting with "AE_", see below). |
|
|
1194 | |
|
|
1195 | All variables can also be set via the "AE_" prefix, that is, instead of |
|
|
1196 | setting "PERL_ANYEVENT_VERBOSE" you can also set "AE_VERBOSE". In case |
|
|
1197 | there is a clash btween anyevent and another program that uses |
|
|
1198 | "AE_something" you can set the corresponding "PERL_ANYEVENT_something" |
|
|
1199 | variable to the empty string, as those variables take precedence. |
|
|
1200 | |
|
|
1201 | When AnyEvent is first loaded, it copies all "AE_xxx" env variables to |
|
|
1202 | their "PERL_ANYEVENT_xxx" counterpart unless that variable already |
|
|
1203 | exists. If taint mode is on, then AnyEvent will remove *all* environment |
|
|
1204 | variables starting with "PERL_ANYEVENT_" from %ENV (or replace them with |
|
|
1205 | "undef" or the empty string, if the corresaponding "AE_" variable is |
|
|
1206 | set). |
|
|
1207 | |
|
|
1208 | The exact algorithm is currently: |
|
|
1209 | |
|
|
1210 | 1. if taint mode enabled, delete all PERL_ANYEVENT_xyz variables from %ENV |
|
|
1211 | 2. copy over AE_xyz to PERL_ANYEVENT_xyz unless the latter alraedy exists |
|
|
1212 | 3. if taint mode enabled, set all PERL_ANYEVENT_xyz variables to undef. |
|
|
1213 | |
|
|
1214 | This ensures that child processes will not see the "AE_" variables. |
|
|
1215 | |
|
|
1216 | The following environment variables are currently known to AnyEvent: |
1174 | |
1217 | |
1175 | "PERL_ANYEVENT_VERBOSE" |
1218 | "PERL_ANYEVENT_VERBOSE" |
1176 | By default, AnyEvent will be completely silent except in fatal |
1219 | By default, AnyEvent will only log messages with loglevel 3 |
1177 | conditions. You can set this environment variable to make AnyEvent |
1220 | ("critical") or higher (see AnyEvent::Log). You can set this |
|
|
1221 | environment variable to a numerical loglevel to make AnyEvent more |
1178 | more talkative. |
1222 | (or less) talkative. |
1179 | |
1223 | |
|
|
1224 | If you want to do more than just set the global logging level you |
|
|
1225 | should have a look at "PERL_ANYEVENT_LOG", which allows much more |
|
|
1226 | complex specifications. |
|
|
1227 | |
|
|
1228 | When set to 0 ("off"), then no messages whatsoever will be logged |
|
|
1229 | with the default logging settings. |
|
|
1230 | |
1180 | When set to 5 or higher, causes AnyEvent to warn about unexpected |
1231 | When set to 5 or higher ("warn"), causes AnyEvent to warn about |
1181 | conditions, such as not being able to load the event model specified |
1232 | unexpected conditions, such as not being able to load the event |
1182 | by "PERL_ANYEVENT_MODEL". |
1233 | model specified by "PERL_ANYEVENT_MODEL", or a guard callback |
|
|
1234 | throwing an exception - this is the minimum recommended level. |
1183 | |
1235 | |
1184 | When set to 7 or higher, cause AnyEvent to report to STDERR which |
1236 | When set to 7 or higher (info), cause AnyEvent to report which event |
1185 | event model it chooses. |
1237 | model it chooses. |
1186 | |
1238 | |
1187 | When set to 8 or higher, then AnyEvent will report extra information |
1239 | When set to 8 or higher (debug), then AnyEvent will report extra |
1188 | on which optional modules it loads and how it implements certain |
1240 | information on which optional modules it loads and how it implements |
1189 | features. |
1241 | certain features. |
|
|
1242 | |
|
|
1243 | "PERL_ANYEVENT_LOG" |
|
|
1244 | Accepts rather complex logging specifications. For example, you |
|
|
1245 | could log all "debug" messages of some module to stderr, warnings |
|
|
1246 | and above to stderr, and errors and above to syslog, with: |
|
|
1247 | |
|
|
1248 | PERL_ANYEVENT_LOG=Some::Module=debug,+log:filter=warn,+%syslog:%syslog=error,syslog |
|
|
1249 | |
|
|
1250 | For the rather extensive details, see AnyEvent::Log. |
|
|
1251 | |
|
|
1252 | This variable is evaluated when AnyEvent (or AnyEvent::Log) is |
|
|
1253 | loaded, so will take effect even before AnyEvent has initialised |
|
|
1254 | itself. |
|
|
1255 | |
|
|
1256 | Note that specifying this environment variable causes the |
|
|
1257 | AnyEvent::Log module to be loaded, while "PERL_ANYEVENT_VERBOSE" |
|
|
1258 | does not, so only using the latter saves a few hundred kB of memory |
|
|
1259 | until the first message is being logged. |
1190 | |
1260 | |
1191 | "PERL_ANYEVENT_STRICT" |
1261 | "PERL_ANYEVENT_STRICT" |
1192 | AnyEvent does not do much argument checking by default, as thorough |
1262 | AnyEvent does not do much argument checking by default, as thorough |
1193 | argument checking is very costly. Setting this variable to a true |
1263 | argument checking is very costly. Setting this variable to a true |
1194 | value will cause AnyEvent to load "AnyEvent::Strict" and then to |
1264 | value will cause AnyEvent to load "AnyEvent::Strict" and then to |
… | |
… | |
1201 | is definitely recommended to keep it off in production. Keeping |
1271 | is definitely recommended to keep it off in production. Keeping |
1202 | "PERL_ANYEVENT_STRICT=1" in your environment while developing |
1272 | "PERL_ANYEVENT_STRICT=1" in your environment while developing |
1203 | programs can be very useful, however. |
1273 | programs can be very useful, however. |
1204 | |
1274 | |
1205 | "PERL_ANYEVENT_DEBUG_SHELL" |
1275 | "PERL_ANYEVENT_DEBUG_SHELL" |
1206 | If this env variable is set, then its contents will be interpreted |
1276 | If this env variable is nonempty, then its contents will be |
1207 | by "AnyEvent::Socket::parse_hostport" (after replacing every |
1277 | interpreted by "AnyEvent::Socket::parse_hostport" and |
1208 | occurance of $$ by the process pid) and an "AnyEvent::Debug::shell" |
1278 | "AnyEvent::Debug::shell" (after replacing every occurance of $$ by |
1209 | is bound on that port. The shell object is saved in |
1279 | the process pid). The shell object is saved in |
1210 | $AnyEvent::Debug::SHELL. |
1280 | $AnyEvent::Debug::SHELL. |
1211 | |
1281 | |
1212 | This takes place when the first watcher is created. |
1282 | This happens when the first watcher is created. |
1213 | |
1283 | |
1214 | For example, to bind a debug shell on a unix domain socket in |
1284 | For example, to bind a debug shell on a unix domain socket in |
1215 | /tmp/debug<pid>.sock, you could use this: |
1285 | /tmp/debug<pid>.sock, you could use this: |
1216 | |
1286 | |
1217 | PERL_ANYEVENT_DEBUG_SHELL=/tmp/debug\$\$.sock perlprog |
1287 | PERL_ANYEVENT_DEBUG_SHELL=/tmp/debug\$\$.sock perlprog |
|
|
1288 | # connect with e.g.: socat readline /tmp/debug123.sock |
1218 | |
1289 | |
|
|
1290 | Or to bind to tcp port 4545 on localhost: |
|
|
1291 | |
|
|
1292 | PERL_ANYEVENT_DEBUG_SHELL=127.0.0.1:4545 perlprog |
|
|
1293 | # connect with e.g.: telnet localhost 4545 |
|
|
1294 | |
1219 | Note that creating sockets in /tmp is very unsafe on multiuser |
1295 | Note that creating sockets in /tmp or on localhost is very unsafe on |
1220 | systems. |
1296 | multiuser systems. |
1221 | |
1297 | |
1222 | "PERL_ANYEVENT_DEBUG_WRAP" |
1298 | "PERL_ANYEVENT_DEBUG_WRAP" |
1223 | Can be set to 0, 1 or 2 and enables wrapping of all watchers for |
1299 | Can be set to 0, 1 or 2 and enables wrapping of all watchers for |
1224 | debugging purposes. See "AnyEvent::Debug::wrap" for details. |
1300 | debugging purposes. See "AnyEvent::Debug::wrap" for details. |
1225 | |
1301 | |
… | |
… | |
1263 | "PERL_ANYEVENT_PROTOCOLS=ipv4" - only support IPv4, never try to |
1339 | "PERL_ANYEVENT_PROTOCOLS=ipv4" - only support IPv4, never try to |
1264 | resolve or contact IPv6 addresses. |
1340 | resolve or contact IPv6 addresses. |
1265 | "PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4" support either IPv4 or IPv6, but |
1341 | "PERL_ANYEVENT_PROTOCOLS=ipv6,ipv4" support either IPv4 or IPv6, but |
1266 | prefer IPv6 over IPv4. |
1342 | prefer IPv6 over IPv4. |
1267 | |
1343 | |
|
|
1344 | "PERL_ANYEVENT_HOSTS" |
|
|
1345 | This variable, if specified, overrides the /etc/hosts file used by |
|
|
1346 | AnyEvent::Socket"::resolve_sockaddr", i.e. hosts aliases will be |
|
|
1347 | read from that file instead. |
|
|
1348 | |
1268 | "PERL_ANYEVENT_EDNS0" |
1349 | "PERL_ANYEVENT_EDNS0" |
1269 | Used by AnyEvent::DNS to decide whether to use the EDNS0 extension |
1350 | Used by AnyEvent::DNS to decide whether to use the EDNS0 extension |
1270 | for DNS. This extension is generally useful to reduce DNS traffic, |
1351 | for DNS. This extension is generally useful to reduce DNS traffic, |
1271 | but some (broken) firewalls drop such DNS packets, which is why it |
1352 | especially when DNSSEC is involved, but some (broken) firewalls drop |
1272 | is off by default. |
1353 | such DNS packets, which is why it is off by default. |
1273 | |
1354 | |
1274 | Setting this variable to 1 will cause AnyEvent::DNS to announce |
1355 | Setting this variable to 1 will cause AnyEvent::DNS to announce |
1275 | EDNS0 in its DNS requests. |
1356 | EDNS0 in its DNS requests. |
1276 | |
1357 | |
1277 | "PERL_ANYEVENT_MAX_FORKS" |
1358 | "PERL_ANYEVENT_MAX_FORKS" |
… | |
… | |
1281 | "PERL_ANYEVENT_MAX_OUTSTANDING_DNS" |
1362 | "PERL_ANYEVENT_MAX_OUTSTANDING_DNS" |
1282 | The default value for the "max_outstanding" parameter for the |
1363 | The default value for the "max_outstanding" parameter for the |
1283 | default DNS resolver - this is the maximum number of parallel DNS |
1364 | default DNS resolver - this is the maximum number of parallel DNS |
1284 | requests that are sent to the DNS server. |
1365 | requests that are sent to the DNS server. |
1285 | |
1366 | |
|
|
1367 | "PERL_ANYEVENT_MAX_SIGNAL_LATENCY" |
|
|
1368 | Perl has inherently racy signal handling (you can basically choose |
|
|
1369 | between losing signals and memory corruption) - pure perl event |
|
|
1370 | loops (including "AnyEvent::Loop", when "Async::Interrupt" isn't |
|
|
1371 | available) therefore have to poll regularly to avoid losing signals. |
|
|
1372 | |
|
|
1373 | Some event loops are racy, but don't poll regularly, and some event |
|
|
1374 | loops are written in C but are still racy. For those event loops, |
|
|
1375 | AnyEvent installs a timer that regularly wakes up the event loop. |
|
|
1376 | |
|
|
1377 | By default, the interval for this timer is 10 seconds, but you can |
|
|
1378 | override this delay with this environment variable (or by setting |
|
|
1379 | the $AnyEvent::MAX_SIGNAL_LATENCY variable before creating signal |
|
|
1380 | watchers). |
|
|
1381 | |
|
|
1382 | Lower values increase CPU (and energy) usage, higher values can |
|
|
1383 | introduce long delays when reaping children or waiting for signals. |
|
|
1384 | |
|
|
1385 | The AnyEvent::Async module, if available, will be used to avoid this |
|
|
1386 | polling (with most event loops). |
|
|
1387 | |
1286 | "PERL_ANYEVENT_RESOLV_CONF" |
1388 | "PERL_ANYEVENT_RESOLV_CONF" |
1287 | The file to use instead of /etc/resolv.conf (or OS-specific |
1389 | The absolute path to a resolv.conf-style file to use instead of |
1288 | configuration) in the default resolver. When set to the empty |
1390 | /etc/resolv.conf (or the OS-specific configuration) in the default |
1289 | string, no default config will be used. |
1391 | resolver, or the empty string to select the default configuration. |
1290 | |
1392 | |
1291 | "PERL_ANYEVENT_CA_FILE", "PERL_ANYEVENT_CA_PATH". |
1393 | "PERL_ANYEVENT_CA_FILE", "PERL_ANYEVENT_CA_PATH". |
1292 | When neither "ca_file" nor "ca_path" was specified during |
1394 | When neither "ca_file" nor "ca_path" was specified during |
1293 | AnyEvent::TLS context creation, and either of these environment |
1395 | AnyEvent::TLS context creation, and either of these environment |
1294 | variables exist, they will be used to specify CA certificate |
1396 | variables are nonempty, they will be used to specify CA certificate |
1295 | locations instead of a system-dependent default. |
1397 | locations instead of a system-dependent default. |
1296 | |
1398 | |
1297 | "PERL_ANYEVENT_AVOID_GUARD" and "PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT" |
1399 | "PERL_ANYEVENT_AVOID_GUARD" and "PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT" |
1298 | When these are set to 1, then the respective modules are not loaded. |
1400 | When these are set to 1, then the respective modules are not loaded. |
1299 | Mostly good for testing AnyEvent itself. |
1401 | Mostly good for testing AnyEvent itself. |