RPM package uses Debian environment file paths in systemd unit file

A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Problem

In RHEL-based Linux distros, service specific environment variable files typically live in/etc/sysconfig (similar to /etc/default in Debian). This location is then referenced in the systemd unit file for a particular service. Here's an example from Fedora 43's rsyslog package:

rpm -ql rsyslog | grep sysconfig # where does the package put its envvar file?
/etc/sysconfig/rsyslog 

cat /etc/sysconfig/rsyslog
# Options for rsyslogd
# Syslogd options are deprecated since rsyslog v3.
# If you want to use them, switch to compatibility mode 2 by "-c 2"
# See rsyslogd(8) for more details
SYSLOGD_OPTIONS=""

systemctl cat rsyslog | grep EnvironmentFile # where does the service look for its envvar files?
EnvironmentFile=-/etc/sysconfig/rsyslog

By contrast, the vector RPM package uses Debian paths:

rpm -ql vector | grep default # where does the package put its envvar file?
/etc/default/vector
systemctl cat vector.service | grep EnvironmentFile
EnvironmentFile=-/etc/default/vector

This isn't a huge deal or anything, but it can be confusing if you're trying to customize the envvar file and it's not in the typical place for RHEL. Thanks for taking a look!

Configuration

N/A

Version

vector 0.57.0 (x86_64-unknown-linux-gnu 8832452 2026-07-14 20:58:30.491174540) , installed via RPM repo

Debug Output

N/A

Example Data

No response

Additional Context

No response

References

No response

Inspect the RPM packaging files and the systemd unit that define Vector's EnvironmentFile path. Compare the generated RPM and unit behavior with the RHEL convention described in the issue, then verify the corrected path by building or installing the RPM and checking the resulting systemd unit.