aboutsummaryrefslogtreecommitdiff
path: root/usr.sbin/syslogd
Commit message (Collapse)AuthorAgeFilesLines
* tests: skip gracefully when the tested binary's own package isn't installedWarner Losh2026-09-111-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | pkgbase splits programs and their tests into separate packages (e.g. unifdef/yacc/indent/file2c -> toolchain, jail -> jail, etc), while their tests always land in the generic tests package. Installing just the tests package therefore leaves these suites unable to find the binary they exercise, and they fail confusingly instead of skipping. Rather than force all packages to be installed for the tests package, make the tests cope with the missing packages. Add require.progs (or, for TAP/PLAIN-style suites with no atf_set hook: TEST_METADATA required_programs) for the binary under test in: bectl, certctl, ctfconvert, dhclient, file2c, indent, ipfw, jail, lastcomm, mixer, newsyslog, nvmecontrol, pfctl, praudit, sa, syslogd, tunefs, unifdef, yacc, ztest. I skipped adding data for all the binaries in the base runtime package for simplicity. Assisted-by: Claude Code (Sonnet 5) Sponsored by: Netflix Reviewed by: ngie Differential Revision: https://reviews.freebsd.org/D58262
* syslogd/tests: Amend a test to catch leaked process descriptorsMark Johnston2026-09-021-0/+7
| | | | | | | This serves to catch the regression fixed by commit 1a669b66ddb4 ("syslogd: reap pipe children on config reload"). MFC after: 1 week
* syslogd: Pipes need the CAP_PDGETPID right as wellMark Johnston2026-09-021-3/+4
| | | | | | | | | | While here, use caph_rights_limit(), as syslogd already uses caph_enter(). PR: 298104 Reported by: mi Fixes: 24816abb8740 ("syslogd: Limit rights on procdescs") MFC after: 3 days
* syslogd: reap pipe children on config reloadBaptiste Daroussin2026-09-021-5/+9
| | | | | | | | | | | | | | | | | | | On SIGHUP reload, closelogfiles() frees each F_PIPE filed even when its pipe process is still running. close_filed() sets f_type to F_UNUSED before the check, so the condition f_type != F_PIPE is always true and the filed is freed while its process descriptor is still on the dead queue and registered in the kqueue. When the child later exits, the NOTE_EXIT handler dereferences the freed filed (use-after-free) and never closes the process descriptor, leaving the pipe child as a persistent zombie. Capture whether the filed is a pipe with an active process descriptor before calling close_filed(), and defer the free in that case so the NOTE_EXIT handler can reap the child and free the filed. Reviewed by: markj Fixes: 95381c0139d6 (syslogd: Use process descriptors) Differential Revision: https://reviews.freebsd.org/D59319
* syslogd: Limit rights on procdescsMark Johnston2026-07-101-0/+5
| | | | | | Reviewed by: jfree, kib MFC after: 3 weeks Differential Revision: https://reviews.freebsd.org/D58160
* syslogd: Handle connection errors when setting up forwarding socketsMark Johnston2026-06-304-25/+188
| | | | | | | | | | | | | | | | | | | | Since syslogd was converted to run in a Capsicum sandbox, it needs to explicitly connect() its forwarding sockets rather than using sendmsg(). At the time syslogd starts during boot, some of its forwarding destinations may not be routable, in which case connect() fails. Fix this by making connect() failures non-fatal, and use cap_net to lazily connect sockets once something actually tries logging to the destination. Add a regression test. Reported by: ae Reviewed by: ae Discussed with: jfree Fixes: 4ecbee2760f7 ("syslogd: Open forwarding socket descriptors") MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D57394
* ttymsg: OverhaulDag-Erling Smørgrav2026-05-254-79/+36
| | | | | | | | | | | | | | | | | | | | | | | | | * Instead of an error string, return the usual 0 or -1 and let the caller figure out what, if anything, to tell the user. * Avoid string manipulations by opening /dev first and using openat() with O_RESOLVE_BENEATH. * Add a boolean argument which, if false, causes ttymsg() to return without sending the message if the tty's group-writable bit is not set. This saves programs that respect this setting (like syslogd(8)) from having to check before calling ttymsg(). * Update all callers. The observable effect of this change is minimal except for slightly different error messages when ttymsg() fails. However, syslogd(8) will no longer print spurious error messages on the console after trying and failing to write a log message to an X11 session. PR: 295171 MFC after: 1 week Reviewed by: jfree, markj Differential Revision: https://reviews.freebsd.org/D57018
* syslogd: fix memory leak in casper_ttymsg()Pat Maddox2026-05-221-8/+6
| | | | | | | | | | | | | | | | | | | | | nvlist_take_string_array(9) takes ownership of the array and its strings. casper_ttymsg() freed neither, leaking memory on every F_CONSOLE and F_TTY message. On long-running systems with high error-rate syslog traffic routed to /dev/console, syslogd.casper grew to hundreds of MB. Use nvlist_get_string_array(9) to borrow the array instead. Update casper_wallmsg() similarly. Approved by: src (des) Closes: https://github.com/freebsd/freebsd-src/pull/2222 Fixes: 61a29eca550b ("syslogd: Log messages using libcasper") MFC after: 3 days MFC to: stable/15 PR: 295488 Reported by: Pat Maddox <pat@patmaddox.com> Reviewed by: markj Tested by: dch
* syslogd: Fix ereregex property filters and add testtzyt2026-03-292-1/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | This change fixes Bug 293879, where ereregex filters in syslogd did not handle alternation correctly. The issue appears to come from mixing up two different kinds of flags: syslogd's internal serialized filter flags in usr.sbin/syslogd/syslogd.h, and the regex compilation flags from include/regex.h. ereregex was storing REG_EXTENDED in cmp_flags, even though cmp_flags is meant to carry syslogd's own FILT_FLAG_* values for configuration serialization and reconstruction. REG_EXTENDED has the same bit value as FILT_FLAG_EXCLUDE, so the filter could be reconstructed with the wrong semantics. The fix stores FILT_FLAG_EXTENDED instead, allowing syslogd to correctly REG_EXTENDED when compiling the regex. A test was also added for both ereregex and !ereregex filters. PR: 293879 Signed-off-by: tzyt <zyt2006613@outlook.com> Fixes: 2567168dc4986 MFC after: 1 week Reviewed-by: markj, ngie Pull-Request: https://github.com/freebsd/freebsd-src/pull/2088
* manuals: System message vs kernel messageAlexander Ziaee2026-03-261-4/+2
| | | | | | | | | | | | | | | | Wordsmith mentions throughout the manual of syslog and dmesg, to clearly differentiate them in an externally consisteny way, increasing operator onboarding speed and elegance. The daemon that handles general system messages, syslog, describes them as "system messages", and "messages" is the standard filename. Rewrite syslog related manual titles to align search results with this, and hier entries to align the index. Use care to maintain keywords and not add extra lines. Newsyslog trades "maintain" with "rotate" for visibility. MFC after: 3 days Reviewed by: markj Closes: https://github.com/freebsd/freebsd-src/pull/2067
* syslogd: Allow killing when in foregroundDag-Erling Smørgrav2026-03-241-2/+8
| | | | | | | | | | Normally, syslogd reacts only to SIGTERM, and ignores SIGINT and SIGQUIT unless in debug mode. Extend that to also apply when running in the foreground. Take this opportunity to comment the event loop. MFC after: 1 week Reviewed by: jfree Differential Revision: https://reviews.freebsd.org/D55886
* syslogd/tests: use kern.features to detect INET supportSiva Mahadevan2026-02-191-2/+1
| | | | | | | | | | | | | | This fixes INET feature detection with kernel configs that do not include the kern.conftxt sysctl, such as riscv64 currently[0]. [0] https://ci.freebsd.org/view/Test/job/FreeBSD-main-riscv64-test/16514/testReport/usr.sbin.syslogd/syslogd_forwarded_format_test/O_flag_bsd_forwarded_legacy/ Reviewed by: markj Approved by: emaste (mentor) MFC after: 3 days Sponsored by: The FreeBSD Foundation Differential Revision: https://reviews.freebsd.org/D55383
* syslogd: Improve handling of configuration errorsMark Johnston2026-02-161-6/+8
| | | | | | | | | | | | | | Make parse_selector() print a warning to stderr and continue parsing the config if it encounters an invalid facility or priority. Note that because the parsing is done from a casper service, there isn't a good mechanism to log errors; the warnings are visible only when syslogd is started in debug mode. Reported by: Doug Hardie <bc979@lafn.org> MFC after: 1 week Fixes: f4b4a10abb26 ("syslogd: Move selector parsing into its own function") Reviewed by: jfree, jlduran, eugen, delphij Differential Revision: https://reviews.freebsd.org/D55033
* syslogd/tests: Fix flakiness in forwarding testsMark Johnston2026-01-222-5/+12
| | | | | | | | | | | | | | | | syslogd_start() waits for the local log socket to appear before returning, to ensure that the daemon is ready to handle log messages. Some tests start two daemons, so by default the socket already exists when the second daemon is started, so syslogd_start() returns early. The test subsequently sends a message to this second daemon, which sometimes isn't ready. Define a separate log socket for the second daemon. Add a check to syslogd_start() to help catch this type of bug. Reviewed by: jlduran MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D54800
* syslogd/tests: Improve loopback interface initializationMark Johnston2026-01-222-7/+5
| | | | | | | | | - In syslogd_start(), assign the lo0 address in the specified jail. - Use the correct netmask. Reviewed by: jlduran MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D54799
* syslogd/tests: Address racesMark Johnston2026-01-226-191/+184
| | | | | | | | | | | | | | | | | | | | | | | | | | | | I occasionally see failures in the syslogd test suite. The problem is that the tests are racy: they send a message using logger(1), then immediately check whether the message was logged to a log file. If the syslogd instance under test doesn't get a chance to run before the second step, the test fails. This change reworks things to avoid the race while minimizing the amount of time sleeping. 1) Each test uses a single logfile, so have them use a new common variable, SYSLOGD_LOGFILE, instead of something test-specific. 2) In syslogd_start(), if the configuration references SYSLOGD_LOGFILE, wait for it to be created by syslogd before returning. 3) Add a helper syslogd_check_log(), to check for a given log entry in the last line of SYSLOGD_LOGFILE, instead of using atf_check directly. 4) In syslogd_check_log(), poll the logfile until the desired log entry appears, or the test times out. With this change, I was able to run the tests 1000 times in a loop with 4-way parallelism without seeing any test failures. Without the change I usually get a failure within 10 loops. Reviewed by: jlduran MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D54779
* syslogd/tests: Use a helper function to log from within a jailMark Johnston2026-01-222-29/+38
| | | | | | | | | | | This is just for consistency with all other logger(1) invocations, which happen from the syslogd_log() function. No functional change intended. Reviewed by: jlduran MFC after: 2 weeks Differential Revision: https://reviews.freebsd.org/D54778
* syslogd: Terminate pipe processes gracefullyJake Freeland2026-01-122-58/+70
| | | | | | | | | Pipe actions spawn a process based on the command provided in the syslogd configuration file. When a HUP signal is received, enter the process into the deadq instead of immediately killing it. This matches the behavior of syslogd prior to it being Capsicumized. Fixes: d2d180fb7736
* Remove ftpd(8)Lexi Winter2025-09-291-6/+0
| | | | | | | | | | | | | | | | | | | | | This was previously deprecated and is slated for removal in 15.0. Users who still need ftpd(8) can install the ftp/freebsd-ftpd port. Retain the ftp(d) PAM services since other FTP daemons use them. Update /etc/inetd.conf to point to /usr/local. Add ftpd to ObsoleteFiles, but do not list configuration files since users may want to preserve these to use with the freebsd-ftpd port. There is still some language in the manual referring to ftpd(8) which is relevant to the port, which has been retained but updated to reference the port. MFC after: 3 days Relnotes: yes Reviewed by: cperciva Differential Revision: https://reviews.freebsd.org/D52739
* syslogd: Make some code more clear.Bryan Drewery2025-09-171-2/+4
| | | | | | | | | | This moves some math to where it logically makes more sense for skipping over the ": " separator in the message formatted "app[PID]: MSG". No functional change. Fixes: 18bcf5a0 ("Restore local kernel "prog" filtering") Sponsored by: Dell Inc.
* syslogd: EAGAIN and ECONNREFUSED are not permanently fatalKristof Provost2025-08-181-3/+2
| | | | | | | | | | | | | | When we're forwarding syslog messages to a remote host we can get temporary failures such as EAGAIN or ECONNREFUSED from the sendmsg() call. These are not fatal. Future attempts to send might succeed. Don't mark the remote target as F_UNUSED so we'll try to log again on future messages. While here remove the commented out ENOBUFS case, because we actually handle that (by ignoring it, so we retry with future logs). Reviewed by: markj, jfree Sponsored by: Rubicon Communications, LLC ("Netgate") Differential Revision: https://reviews.freebsd.org/D51995
* syslogd.8: Remove incorrect .AqLexi Winter2025-08-151-1/+1
| | | | | | | | | Using .Aq is wrong here, because the protocol says the prefix must use ASCII <>. MFC after: 3 days Reviewed by: imp Differential Revision: https://reviews.freebsd.org/D51880
* syslogd: Fix function return testNathan Huff2025-07-301-1/+1
| | | | | | | | | | Looks like during the capsicum setup the return value for cap_syslogd is checked twice rather than checking the return value of cap_net after initializing the casper service. Signed-off-by: Nathan Huff <nhuff@acm.org> Fixes: 897240c7d666 ("syslogd: Enter capability mode") Pull-request: https://github.com/freebsd/freebsd-src/pull/1796
* syslogd: Fix tests when if_epair is not loadedJose Luis Duran2025-02-122-11/+55
| | | | | | | | | | | | | | Take a cue from vnet.subr and abstract module loading, jail creation and cleanup. Note that the way jails are created differs slightly from vnet.subr, to maintain the current style of the tests. Reported by: Jenkins Reviewed by: markj Approved by: emaste (mentor) MFC after: 1 week Differential Revision: https://reviews.freebsd.org/D48949
* syslogd: Ensure that forwarded messages are sent from port 514Mark Johnston2025-01-144-25/+378
| | | | | | | | | | | | | | | | | | | | | | | | | | | Prior to commit 4ecbee2760f7, syslogd used its listening socket(s) to forward messages to remote hosts, when so configured. As a consequence, they are sent from the address+port to which those sockets are bound, typically 0.0.0.0:514. When in capability mode, sendto() is not permitted, so we instead pre-create sockets and connect them to the forwarding addresses, letting the kernel pick an ephemeral source port. However, this doesn't match syslogd's previous behaviour, breaking some setups. So, restore the old behaviour by binding forwarding sockets to the addresses on which syslogd is listening. Since we cannot use the same sockets for receiving messages and also for forwarding them, use SO_REUSEPORT to enable duplicate bindings to port 514, relying on the existing behaviour that the first socket bound to that port is the one that actually receives messages. Add some regression tests to cover this and related functionality of syslogd's -a option. Reviewed by: jfree Reported by: Michael Butler <imb@protected-networks.net> Fixes: 4ecbee2760f7 ("syslogd: Open forwarding socket descriptors") Differential Revision: https://reviews.freebsd.org/D48222
* syslogd: Fix resource leaksMark Johnston2025-01-031-17/+15
| | | | | | | | | | | | | | | | - nvlist_append_nvlist_array() makes a copy of the input nvlist, so the pattern of nvlist_append_nvlist_array(... cfline(...)) would leak memory and descriptors. Pass the entire config nvlist to cfline() instead since this is needed for a future change. - In parse_action(), free the linked list returned by getaddrinfo(). - Remove some checks at the beginning of close_filed(). For some log types we'll always have f->f_file == -1, in which case we wouldn't release other resources, such as forwarding sockets. - After converting a filed to an nvlist, free the filed resources. Fixes: 2567168dc498 ("syslogd: Refresh configuration using libcasper") Reviewed by: jfree Differential Revision: https://reviews.freebsd.org/D48250
* syslogd tests: Permit starting syslogd with multiple -b optionsMark Johnston2025-01-031-3/+3
|
* syslogd tests: Use atf_check when sending SIGHUP to syslogdMark Johnston2025-01-031-1/+1
|
* syslogd: Add rfc3164-strict format optionMichal Scigocki2024-12-235-11/+107
| | | | | | | | | | | | | | | The syslogd bsd/rfc3164 message format does not strictly conform to the format recommended in RFC 3164 when syslog messages are forwarded from remote hosts. The new rfc3164-strict format generates messages that conform with the RFC 3164 recommended format. The existing format is maintained for backwards compatibility. PR: 220246 Reviewed by: markj MFC after: 3 weeks Pull Request: https://github.com/freebsd/freebsd-src/pull/1536
* syslogd: Add syslog relayed message format testsMichal Scigocki2024-12-232-0/+163
| | | | | | Reviewed by: markj MFC after: 3 weeks Pull Request: https://github.com/freebsd/freebsd-src/pull/1536
* syslogd: Add syslog forwarded message format testsMichal Scigocki2024-12-234-1/+270
| | | | | | Reviewed by: markj MFC after: 3 weeks Pull Request: https://github.com/freebsd/freebsd-src/pull/1536
* syslogd: Add syslog basic message format testsMichal Scigocki2024-12-235-106/+270
| | | | | | | | | RFC 3164 and RFC 5424 syslog message format tests and minor refactor of existing tests to reuse components in new tests. Reviewed by: markj MFC after: 3 weeks Pull Request: https://github.com/freebsd/freebsd-src/pull/1536
* syslogd: Remove is_exclusive metadata from testsMichal Scigocki2024-12-231-6/+4
| | | | | | | | | | - Tests have been updated to use "jail" execution environment, is_exclusive="true" is no longer required. - tests/Makefile update to style.Makefile(5). Reviewed by: markj MFC after: 3 weeks Pull Request: https://github.com/freebsd/freebsd-src/pull/1536
* syslogd: Fix issues reported by gccMark Johnston2024-11-301-2/+1
| | | | | | | | | | | - When forwaring a message, don't assume that f->f_num_addr_fds > 0. - Avoid calling free() on a stack-allocated object. Fixes: 4ecbee2760f7 ("syslogd: Open forwarding socket descriptors") Fixes: f4b4a10abb26 ("syslogd: Move selector parsing into its own function") Reviewed by: jfree Differential Revision: https://reviews.freebsd.org/D47844
* syslogd: Split up basic test caseJake Freeland2024-11-271-23/+60
| | | | | | | | | | | | | The basic case previously tested if messages are correctly logged over UNIX, INET, and INET6 transport. This single case can be split up into three separate cases to decrease code complexity and offer more granular results. Both INET and INET6 cases will be skipped if the kernel does not support the corresponding transport. Reviewed by: zlei, markj Differential Revision: https://reviews.freebsd.org/D47650
* syslogd: Add host forwarding testJake Freeland2024-11-272-19/+110
| | | | | | | | | | | | | | | | | Test communication between hosts by setting up two syslogd instances, each binded to their own addresses, and sending a message from one to the other. The tests passes if the message was delivered and logged successfully. This required some tweaking to the syslogd start and stop routines so they could handle launching multiple syslogd instances with different runtime files. Run the tests in jails with an isolated VNET so they don't fail due to an address bind collision in the host's VNET. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D47649
* syslogd: Open forwarding socket descriptorsJake Freeland2024-11-273-68/+115
| | | | | | | | | | | | | | | | | Previously, when forwarding a message to a remote address, the target's addrinfo was saved at config-parse-time. When message-deliver-time came, the message's addrinfo was passed into sendmsg(2) and delivered by the first available inet socket. Passing an addrinfo into sendmsg(2) is prohibited in Capsicum capability mode, so sockets are now opened and connected to their remote peers at config-parse-time when executing outside of the capability sandbox. These connected socket descriptors are saved and passed into sendmsg(2), allowing forwarding to be performed inside of the capability sandbox. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D47104
* syslogd: Watch for dead pipe processesJake Freeland2024-11-272-15/+81
| | | | | | | | | | For each new pipe process, add its process descriptor into the kqueue with the EVFILT_PROCDESC filter and NOTE_EXIT event. When the pipe process exits, the main kqueue loop will catch this, logging exit errors and cleaning up the pipe process' filed node. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D41477
* syslogd: Enter capability modeJake Freeland2024-11-272-9/+60
| | | | | | | | | | | | Create syslogd_cap_enter() function, which puts syslogd in capability mode and opens necessary libcasper channels for resource acquisition. The `syslogd.casper` and `system.net` services are used. Substitute capability-mode-unfriendly functions with their libcasper `cap_` equivalents. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D41467
* syslogd: Block timezone updating in capability modeJake Freeland2024-11-271-0/+6
| | | | | | | | | | Do not update local timezone data upon reload when syslogd is compiled with libcasper support. Timezone files are pre-fetched using the caph_cache_tzdata() function before entering capability mode. Attempts to re-fetch these files will result in a capability violation. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D41466
* syslogd: Log messages using libcasperJake Freeland2024-11-277-43/+330
| | | | | | | | | | | | | | | Some logging operations require access to external resources to complete. Logging to F_WALL requires on-demand access to the user accounting database. Logging to F_CONSOLE requires access to the console. Logging to F_PIPE prompts execution of a command outside of capability mode. These operations cannot be performed in capability mode, so the "p_open", "ttymsg", and "wallmsg" commands may be sent to libcasper to circumvent these limitations. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D41465
* syslogd: Refresh configuration using libcasperJake Freeland2024-11-276-135/+436
| | | | | | | | | | | | | | | | When a SIGHUP signal is sent to syslogd, the configuration is reparsed, leading to new resource acquisition. If syslogd is running in capability mode and a SIGHUP is received, new resources cannot be acquired. To mitigate this issue, libcasper is used to parse the configuration. The libcasper process runs outside of capability mode and is capable of parsing syslogd's configuration and obtaining new resources. These resources are then sent to the syslogd process via nvlist. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D41464
* syslogd: Use anonymous union in struct filedJake Freeland2024-11-272-59/+50
| | | | | | | | Do not use macros to access unioned struct members. Use an anonymous union and access union member names directly. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D41703
* syslogd: Create syslogd libcasper serviceJake Freeland2024-11-275-116/+287
| | | | | | | | | | | | | | | | | Once in capability mode, resource acquisition is not possible. To mitigate this, introduce a libcasper service that is responsible for fetching and returning new, requested resources to syslogd. Some resources must be packed into an nvlist to be properly transferred between syslogd and the libcasper process. The filed_to_nvlist() and nvlist_to_filed() functions are included to ease the packing process for filed structures. Two additional syslogd.h and syslogd_cap.h header files are included with shared declarations. Reviewed by: markj Differential Revision: https://reviews.freebsd.org/D41463
* syslogd: Fix handling of unix socket modesMark Johnston2024-11-051-1/+13
| | | | | | | | | | When bind() is called, the process umask is applied, so one has to either clear the umask before binding or call chmod() to add permissions after the fact. Do the former here to ensure that the socket always has the correct mode. Reported by: Lexi Winter <lexi@le-fay.org> Fixes: 2b8c3a05e0a6 ("syslogd: Set unix socket modes atomically")
* syslogd: Set unix socket modes atomicallyMark Johnston2024-11-031-5/+5
| | | | | | | Take advantage of the ability to atomically set unix socket modes to ensure that /var/run/logpriv always has mode 0600. MFC after: 1 month
* syslogd: Ignore getaddrinfo() errors if -ss is specifiedMark Johnston2024-09-192-1/+41
| | | | | | | | | | This can arise if the jail doesn't have networking configured, and if -ss is specified, syslogd won't listen on port 514 anyway. Add a regression test case for this as well. PR: 238006 MFC after: 1 month
* Remove residual blank line at start of MakefileWarner Losh2024-07-151-1/+0
| | | | | | | This is a residual of the $FreeBSD$ removal. MFC After: 3 days (though I'll just run the command on the branches) Sponsored by: Netflix
* package: move lpr into its own packageLexi Winter2024-04-191-1/+4
| | | | | Reviewed by: imp Pull Request: https://github.com/freebsd/freebsd-src/pull/1171
* Remove copyright strings ifdef'd outWarner Losh2023-11-271-10/+0
| | | | | | | | | | | We've ifdef'd out the copyright strings for some time now. Go ahead and remove the ifdefs. Plus whatever other detritis was left over from other recent removals. These copyright strings are present in the comments and are largely from CSRG's attempt at adding their copyright to every binary file (which modern interpretations of the license doesn't require). Sponsored by: Netflix
generated by cgit v1.3 (git 2.53.0) at 2026-10-03 05:39:16 +0000