I don't have my file handy, but I set the env var using the Environment directive https://coreos.com/os/docs/latest/using-environment-variables-in-systemd-units.html
So something like: [Service] Environment=RSYNC_PROXY=proxy.example.com:3128 ... I'd propose that cobbler should add an EnvironmentFile directive to the unit file pointed to something like /etc/sysconfig/cobblerd which could be distributed empty and marked as a config file. That way these sorts of things can be done easily. On Nov 13, 2016 19:35, "Ed - 0x1b, Inc." <[email protected]> wrote: > > I could use a description of how you made it work - could you publish > the cobblerd.service file that makes it work for you? If you modify a > *.service file, putting it in /etc/systemd/system protects your > modifications from getting overwritten during an upgrade. > > I have not had luck getting Cobbler to work with a proxy - curl just > fails - I have taken to fronting Cobbler with mrepo, mrepo works with > proxies. YMMV > Thanks > > On Sun, Nov 13, 2016 at 4:34 PM, <[email protected]> wrote: > > I'm trying to do a cobbler import via rsync, but I need to set a proxy server. Is there a 'correct' way to do this? I've gotten it to work by setting RSYNC_PROXY in the cobblerd environment using the systemd unit file. But, I'd prefer to avoid modifying files installed by rpm that aren't marked as config. > > _______________________________________________ > > cobbler mailing list -- [email protected] > > To unsubscribe send an email to [email protected] > _______________________________________________ > cobbler mailing list -- [email protected] > To unsubscribe send an email to [email protected]
_______________________________________________ cobbler mailing list -- [email protected] To unsubscribe send an email to [email protected]
