Synchronet v3.19b-Win32 (install) has been released (Jan-2022).

You can donate to the Synchronet project using PayPal.

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
config:semfiles [2018/03/01 12:21] – old revision restored digital manconfig:semfiles [2019/02/14 22:08] – Added Clear Failed Login List semaphore file and updated other text digital man
Line 1: Line 1:
 ====== Semaphore Files ====== ====== Semaphore Files ======
  
-Synchronet supports a variety of semaphore files which can be used to externally trigger operations of the various servers and services.+Synchronet supports a variety of semaphore files which can be used to externally-trigger internal-operations of the various servers and services.
  
-The contents of a sempahore file are not relavent; the mere existence or updated date/time stamp of the file is enough to trigger the operation.+The //contents// of semaphore files are not relevant; the mere existence or updated date/time stamp of the file is enough to trigger the operation.
  
-Semaphore file can be create or their date/time stamp updated with simple command-line operations.+Semaphore files can be created or their date/time stamp updated with simple command-line operations.
  
 Windows: Windows:
Line 14: Line 14:
      
  
-===== Existence Semfiles =====+===== Existence Semaphore Files =====
  
 These semaphore files just need to be merely created to trigger the operation and the semaphore file will be automatically deleted: These semaphore files just need to be merely created to trigger the operation and the semaphore file will be automatically deleted:
  
-==== Event Semfiles ====+==== Event Semaphore Files ====
  
 Events that have been configured in [[util:SCFG]]->External Programs->Timed Events can be externally triggered by creating the file ''[[dir:data]]///<event>//.now'', where ''//<event>//'' is the "Internal Code" if the timed event. Events are executed (serially) by the [[server:terminal|Terminal Server]] Event Thread. Events that have been configured in [[util:SCFG]]->External Programs->Timed Events can be externally triggered by creating the file ''[[dir:data]]///<event>//.now'', where ''//<event>//'' is the "Internal Code" if the timed event. Events are executed (serially) by the [[server:terminal|Terminal Server]] Event Thread.
Line 26: Line 26:
   # touch /sbbs/data/fidoin.now   # touch /sbbs/data/fidoin.now
      
-==== QWK Pack Semfiles ====+==== QWK Pack Semaphore Files ====
  
 QWK message packets can be created for specific user accounts by creating the file ''[[dir:data]]/pack//<user>//.now'' where ''//<user>//'' is the number of the user account to to create the packet for.   QWK message packets can be created for specific user accounts by creating the file ''[[dir:data]]/pack//<user>//.now'' where ''//<user>//'' is the number of the user account to to create the packet for.  
Line 36: Line 36:
 QWK packets are created in the ''[[dir:data]]/file'' directory with a filename of ''//<user>//.qwk''. If a QWK packet already exists for the user, it will be opened and appended with any new messages. QWK packets are created in the ''[[dir:data]]/file'' directory with a filename of ''//<user>//.qwk''. If a QWK packet already exists for the user, it will be opened and appended with any new messages.
  
-==== QWK Pre-pack Semfile ====+==== QWK Pre-pack Semaphore File ====
  
 The QWK pre-pack event (which runs automatically once a day) can be forced by creating the file ''[[dir:data]]/prepack.now''. The QWK pre-pack event (which runs automatically once a day) can be forced by creating the file ''[[dir:data]]/prepack.now''.
  
-==== QWKnet Call-out Semfile ====+==== QWKnet Call-out Semaphore File ====
  
 QWK Network hub call-out events can be forced to execute by creating the file ''[[dir:data]]/qnet///<hub-id>//.qwk'', where ''//<hub-id//'' is the QWK-ID of the QWKnet Hub configured in [[util:SCFG]]->Networks->QWK. QWK Network hub call-out events can be forced to execute by creating the file ''[[dir:data]]/qnet///<hub-id>//.qwk'', where ''//<hub-id//'' is the QWK-ID of the QWKnet Hub configured in [[util:SCFG]]->Networks->QWK.
Line 48: Line 48:
   # touch /sbbs/data/qnet/vert.now   # touch /sbbs/data/qnet/vert.now
  
-===== Timestamp Semfiles =====+===== Timestamp Semaphore Files =====
  
 These semaphore files are not deleted when the operation is triggered, so the date/time stamp of the file must be updated (i.e. the file must be "touched") to trigger the operation again: These semaphore files are not deleted when the operation is triggered, so the date/time stamp of the file must be updated (i.e. the file must be "touched") to trigger the operation again:
  
-==== Recycle Semfiles ====+On a multi-host BBS, the servers and services on a specific host can be signaled by "touching" the file ''[[dir:ctrl]]/<semfile>.//<hostname>//'' or ''[[dir:ctrl]]/<semfile>.//<host.domainname>//'' instead.
  
-Synchronet servers and services can be forced to terminate all threads, close sockets, and reload their configuration files by "touching" the file ''[[dir:ctrl]]/recycle''.+A specific server or service may be signaled by "touching" the file ''[[dir:ctrl]]/<semfile>.//<service>//'' instead, where ''//<service>//'' is one of: ''term, ftp, mail, web, or services''.
  
-On a multi-host BBS, the servers and services on a specific host can be recycled by "touching" the file ''[[dir:ctrl]]/recycle.//<hostname>//'' or ''[[dir:ctrl]]/recycle.//<host.domainname>//'' instead.+==== Recycle Semaphore Files ====
  
-A specific server or service may be recycled by "touching" the file ''[[dir:ctrl]]/recycle.//<service>//'' instead, where ''//<service>//'' is one of: ''telnet, ftp, mail, web, or services''.+Synchronet servers and services can be forced to terminate all threads, close sockets, and reload their configuration files by "touching" the file ''[[dir:ctrl]]/recycle''.
  
 Servers or services that have the ''NO_RECYCLE'' option flag set (in the ''[[sbbs.ini]]'' file) will **not** be recycled by external touching of the //recycle// semaphore file. Servers or services that have the ''NO_RECYCLE'' option flag set (in the ''[[sbbs.ini]]'' file) will **not** be recycled by external touching of the //recycle// semaphore file.
  
-==== Shutdown Semfiles ====+==== Shutdown Semaphore Files ====
  
 Synchronet servers and services can be forced to terminate (shutdown) by "touching" the file ''[[dir:ctrl]]/shutdown''. Synchronet servers and services can be forced to terminate (shutdown) by "touching" the file ''[[dir:ctrl]]/shutdown''.
  
-On a multi-host BBS, the servers and services on a specific host can be recycled by "touching" the file ''[[dir:ctrl]]/shutdown.//<hostname>//'' or ''[[dir:ctrl]]/shutdown.//<host.domainname>//'' instead. +==== Clear Failed Login List Semaphore Files ====
- +
-A specific server or service may be shutdown by "touching" the file ''[[dir:ctrl]]/shutdown.//<service>//'' instead, where ''//<service>//'' is one of: ''telnet, ftp, mail, web, or services''.+
  
 +A sysop can clear the in-memory //Failed Login (temporary IP ban) List// by "touching" the file ''[[dir:ctrl]]/clear''.
  
 ===== See Also ===== ===== See Also =====
   * [[:config:|Configuration]]   * [[:config:|Configuration]]
  
-{{tag>}}+{{tag>filters semfiles events}}
  

Trace: