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 revision		Previous revision
config:semfiles [2022/03/14 20:14] – [See Also] Andreconfig:semfiles [2024/01/12 17:25] (current) – [QWKnet Timed-event Semaphore Files] Add pause semaphore file details digital man
Line 3: Line 3:
 Synchronet supports a variety of semaphore files which can be used to externally-trigger internal-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 semaphore files are not relevant; 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 coresponding operation.
  
-Semaphore files can be created 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. For example:
  
-Windows:+on Windows:
   C:\>echo. > \sbbs\data\dothing.now   C:\>echo. > \sbbs\data\dothing.now
  
-UNIX: +on UNIX: 
-  # touch /sbbs/data/dothing.now+  $ touch /sbbs/data/dothing.now
      
  
 ===== Existence Semaphore Files ===== ===== Existence Semaphore Files =====
  
-These semaphore files just need to be merely created to trigger the operation and the semaphore file will be automatically deleted:+Existence semaphore files just need to be merely created to trigger the corresponding operation and the semaphore file will be automatically deleted:
  
 ==== Sysop Available for Chat ==== ==== Sysop Available for Chat ====
Line 22: Line 22:
 ==== Event Semaphore Files ==== ==== 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" of the corresponding timed event. Events are executed (serially, by default) by the [[server:terminal|Terminal Server]] //Event Thread//.
  
 Example (forcing execution of the FidoNet import event): Example (forcing execution of the FidoNet import event):
  
-  # touch /sbbs/data/fidoin.now+  $ touch /sbbs/data/fidoin.now
      
 ==== QWK Pack Semaphore Files ==== ==== QWK Pack Semaphore Files ====
Line 34: Line 34:
 Example (forcing the creation of a QWK packet for user #1): Example (forcing the creation of a QWK packet for user #1):
  
-  # touch /sbbs/data/pack0001.now+  $ touch /sbbs/data/pack0001.now
      
 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.
Line 48: Line 48:
 Example (forcing QWK call-out to QWKnet hub //VERT//): Example (forcing QWK call-out to QWKnet hub //VERT//):
  
-  # touch /sbbs/data/qnet/vert.now+  $ touch /sbbs/data/qnet/vert.now
      
 ==== QWKnet Timed-event Semaphore Files ==== ==== QWKnet Timed-event Semaphore Files ====
 After receiving and processing a QWKnet ''.QWK'' or ''.REP'' file, Synchronet will //touch// the ''[[dir:data]]/**qnet-qwk**.now'' or ''[[dir:data]]/**qnet-rep**.now'' files to trigger timed events of those names, if they exist, to execute. After receiving and processing a QWKnet ''.QWK'' or ''.REP'' file, Synchronet will //touch// the ''[[dir:data]]/**qnet-qwk**.now'' or ''[[dir:data]]/**qnet-rep**.now'' files to trigger timed events of those names, if they exist, to execute.
  
 +==== Pause Server Semaphore File ====
 +The existence of the file ''[[dir:ctrl]]/pause'' (or a supported service/host variant) will cause that server to stop accepting incoming client connections. Any existing clients/connections will continued to be service while the server is paused. Removing the file will "resume" the server.
 ===== Timestamp Semaphore Files ===== ===== 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:+Timestamp 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:
  
 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. 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.

Trace: