search for: workoround

This has been asked before, but my question is somewhat different. On FreeBSD, the message: rsyncd[520]: /etc/pwd.db: No such file or directory is obviously caused by a chrooted rsyncd being unable to access /etc/pwd.db to get at the password database to convert UIDs to names and back. Workorounds of putting /etc/pwd.db in the chrooted directory have been offered, and that's one solution. However, my questions are these: 1) Does it hurt anything for rsyncd to not be able to resolve uids? It doesn't seem to affect the function of the system. 2) If it's not hurting anything,...

...nstructions. root at inizai# gcc --version gcc (Debian 8.2.0-4) 8.2.0 Copyright (C) 2018 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Is that a known issue? Any workoround or fix available? Regards, - Sedat -

...an 8.2.0-4) 8.2.0 >> Copyright (C) 2018 Free Software Foundation, Inc. >> This is free software; see the source for copying conditions. There is NO >> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >> >> Is that a known issue? >> Any workoround or fix available? >> > > Building with my selfmade llvm-toolchain was successful. > So this seems to be a GCC bug. I tried building the 7.0.0 branch with a vanilla gcc 8.2.0 build, but I couldn't reproduce the error. Have you reported the bug to the gcc bugzilla? Even if it...

...2018 Free Software Foundation, Inc. >>>> This is free software; see the source for copying conditions. There is NO >>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >>>> >>>> Is that a known issue? >>>> Any workoround or fix available? >>>> >>> >>> Building with my selfmade llvm-toolchain was successful. >>> So this seems to be a GCC bug. >> >> I tried building the 7.0.0 branch with a vanilla gcc 8.2.0 build, but >> I couldn't reproduce the error. >...

...;>>>>> This is free software; see the source for copying conditions. There is NO >>>>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. >>>>>> >>>>>> Is that a known issue? >>>>>> Any workoround or fix available? >>>>>> >>>>> >>>>> Building with my selfmade llvm-toolchain was successful. >>>>> So this seems to be a GCC bug. >>>> >>>> I tried building the 7.0.0 branch with a vanilla gcc 8.2.0 build, but &...