Environment variables in systemd
by William Brown
Hi there,
There have been a few changes to systemd files recently so I wanted to check about how to correctly supply environment variables to the server. For example, KRB5_KTNAME. Are we doing this still by EnvironmentFile? Or by another method?
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs
4 years, 9 months
Issue with building RPMs with ASAN_ON
by Simon Pichugin
Hi team,
I'm in the process of creating a Vagrant file which is close to the customer's ENV.
It is heavilly based on Viktor's beaker task.
I use it for building and testing my code. And it is pretty important to build with ASAN.
Currently, what I do is:
1. Set 'ASAN_ON = 1' in rpm.mk
2. Run `make -f rpm.mk srpms` target
3. Build the RPM using `mock -q my_generated.srpm`
4. Install it
Then I've tried running `dscreate` manually or running tests with py.test.
Every time I have the same error here: /run/dirsrv/ns-slapd-standalone1.asan.XXXXX
==22487==LeakSanitizer has encountered a fatal error.
==22487==HINT: For debugging, try setting environment variable LSAN_OPTIONS=verbosity=1:log_threads=1
==22487==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)
I've tried setting `export LSAN_OPTIONS=verbosity=1:log_threads=1` and run once again.
Same issue.
Did anybody encountered the issue? Maybe, Viktor or William, could you please check?
I'm putting the Vagrantfile to the attachments so you can reproduce.
Just run: `ASAN=on vagrant up` from the directory with Vagrantfile.
William, I think, libvirt is present on SUSE so you should have no issues with this too...
Thanks,
Simon
4 years, 9 months