Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
Synchronet
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Main
Synchronet
Commits
afe11b61
Commit
afe11b61
authored
21 years ago
by
deuce
Browse files
Options
Downloads
Patches
Plain Diff
Added some notes regarding setting up syslogd
parent
209c6355
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/sbbscon.txt
+14
-1
14 additions, 1 deletion
docs/sbbscon.txt
with
14 additions
and
1 deletion
docs/sbbscon.txt
+
14
−
1
View file @
afe11b61
...
...
@@ -140,7 +140,20 @@ root, you will have to set the User and Group values.
If you want Synchronet to fork and run in the background as a daemon, logging
via syslog rather than the local console, set Daemonize=True in this section.
The use of the LogFacility setting is beyond the scope of this document.
To configure syslog and the LogFacility, a good default to use is LogFacility=3
Then, in /etc/syslog.conf you will need to add the line:
local3.* /var/log/synchronet.log
You will have to create this file manually initially by running:
touch /var/log/synchronet.log
The send a HUP to syslogd like so:
killall -HUP syslogd
You will want to investigate how your system rotates logs and set it up to
rotate synchronet.log also.
Further use of the LogFacility setting is beyond the scope of this document.
Read your syslog.conf manpage for more information about this. In particular,
do NOT use the 'S' setting unless you are familiar with advanced syslogd
configuration. The S setting will use different facilities for each feature
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment