Update to ngircd 25 #4
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the image to the latest ngircd version. I found it easiest to just go to a newer version of ubuntu for this since the default repository contains the newest version:
https://packages.ubuntu.com/search?keywords=ngircd&searchon=names
I updated the configuration with the changes in the latest sample configuration from the ngircd project. I went back to the default IP binding since ngircd was complaining about being unable to bind to 192.168.0.1 on startup. I also made PAM optional since otherwise unregistered access would no longer be possible. All other settings remain unchanged/default.
Unfortunately, busybox-syslogd behaves differently now. Something in the installation doesn't work quite as intended. I found that this can be easily worked around by just starting syslogd manually. Although probably not intended, this works just fine. The place where it writes the log also changed for whatever reason.