-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
%n is not replaced with the user's ID #70
Comments
I get a similar issue with Running in verbose mode yields this:
So the username resolution went fine on I suspect a missing I used the stdin fetch method. @lahwaacz what did you use? |
There is a call to replacepath in parse.y, and adding an update_tags() to it did the work for my case. I'm giving you a patch... |
I can't upload a patch file (browser crashing), so here it goes:
To apply it:
And rebuild. @lahwaacz: does it work for you? |
Applied now, thanks! |
The above patch makes fdm segfault when
Cheers. |
Try master now please.
…On Fri, Dec 27, 2019 at 10:17:16PM -0800, Gaetan Bisson wrote:
The above patch makes fdm segfault when conf.def_user is NULL. I'm happy
to define default-user in my fdm.conf but did not think this was a
requirement. For reference, here's the backtrace of said segfault:
#0 0x00007ffff7949bcd in _nss_files_getpwnam_r () from /usr/lib/libnss_files.so.2
#1 0x00007ffff7a88a13 in getpwnam_r@@GLIBC_2.2.5 () from /usr/lib/libc.so.6
#2 0x00007ffff7a882fc in getpwnam () from /usr/lib/libc.so.6
#3 0x000055555556f990 in passwd_lookup (user=0x0) at lookup-passwd.c:36
#4 0x000055555556fac8 in user_lookup (user=0x0, order=0x555555598510) at lookup.c:35
#5 0x000055555557b08a in yyparse () at parse.y:461
#6 0x000055555557e087 in parse_conf (path=<optimized out>, macros=0x7fffffffbcb0) at parse.y:83
#7 0x000055555555b3c4 in main (argc=1, argv=0x7fffffffe3a0) at fdm.c:459
Cheers.
-
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Thanks. Master works perfectly now. |
When I
set lock-file "/run/user/%n/fdm.lock"
, I get this error:According to the manual,
%n
should be replaced with "The delivery user's uid." Butset lock-file "%h/.cache/fdm.lock"
works as expected, so "The delivery user's home directory." is expanded...The text was updated successfully, but these errors were encountered: