Merge "modules.conf.sample: Update preload usage documentation."

configs/samples/modules.conf.sample

@@ -8,26 +8,26 @@
 autoload=yes
 ;
 ; Any modules that need to be loaded before the Asterisk core has been
-; initialized (just after the logger has been initialized) can be loaded
+; initialized (just after the logger initialization) can be loaded
-; using 'preload'. This will frequently be needed if you wish to map all
+; using 'preload'.  'preload' forces a module and the modules it
-; module configuration files into Realtime storage, since the Realtime
+; is known to depend upon to be loaded earlier than they normally get
-; driver will need to be loaded before the modules using those configuration
+; loaded.
-; files are initialized.
 ;
-; An example of loading ODBC support would be:
+; NOTE: There is no good reason left to use 'preload' anymore.  It was
-;preload => res_odbc.so
+; historically required to preload realtime driver modules so you could
-;preload => res_config_odbc.so
+; map Asterisk core configuration files to Realtime storage.
+; This is no longer needed.
 ;
-; Uncomment the following if you wish to use the Speech Recognition API
+;preload => your_special_module.so
-;preload => res_speech.so
 ;
 ; If you want Asterisk to fail if a module does not load, then use
 ; the "require" keyword. Asterisk will exit with a status code of 2
 ; if a required module does not load.
 ;
-; require = chan_sip.so
+; require = chan_pjsip.so
+;
 ; If you want you can combine with preload
-; preload-require = res_odbc.so
+; preload-require = your_special_module.so
 ;
 ;load => res_musiconhold.so
 ;