search for: execvp

...a bug in busybox now that POSIX is moving towards > standardizing realpath, so I've filed it: > https://bugs.busybox.net/show_bug.cgi?id=15466 I've found another busybox bug. The "/bin/sh" utility is provided by busybox as well (via the usual symlinking). Per POSIX, if execvp(file, { argv[0], argv[1], ..., NULL }) were to fail with -1/ENOEXEC, then execvp() must retry "as if" with execv(<shell path>, { argv[0], file, argv[1], ..., NULL }) In other words, if direct execution of "file" failed because "file" "has the appropriat...

These patches have been pushed (f5a065aa3a9c..9075f68ffc8b); I'm posting them for visibility. Laszlo Laszlo Ersek (3): lib/test-fork-safe-execvpe.sh: generalize "run" to "run0" lib/test-fork-safe-execvpe.sh: cope with Alpine Linux / BusyBox limitations Revert "ci: skip "lib/test-fork-safe-execvpe.sh" on Alpine Linux" ci/skipped_tests | 10 ---- lib/test-fork-safe-execvpe.sh | 63...

...s >> standardizing realpath, so I've filed it: >> https://bugs.busybox.net/show_bug.cgi?id=15466 > > I've found another busybox bug. > > The "/bin/sh" utility is provided by busybox as well (via the usual symlinking). > > Per POSIX, if > > execvp(file, { argv[0], argv[1], ..., NULL }) > > were to fail with -1/ENOEXEC, then execvp() must retry "as if" with > > execv(<shell path>, { argv[0], file, argv[1], ..., NULL }) > > In other words, if direct execution of "file" failed because "file&...

On 10/1/19 9:11 AM, Richard W.M. Jones wrote: > On Tue, Oct 01, 2019 at 08:24:33AM -0500, Eric Blake wrote: >>> +#else /* !HAVE_EXECVPE */ >>> + SET_NEXT_STATE (%.DEAD) >>> + set_error (ENOTSUP, "platform does not support socket activation"); >>> + return 0; >>> +#endif >> >> We probably ought to add a matching nbd_supports_socket_activation() >> feature function....

On Sun, Mar 19, 2023 at 10:41:37AM +0100, Laszlo Ersek wrote: > This is version 4 of the following sub-series: > > [libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe() > [libnbd PATCH v3 10/29] lib/utils: add unit tests for async-signal-safe execvpe() > > http://mid.mail-archive.com/20230215141158.2426855-10-lersek at redhat.com > http://mid.mail-archive.com/20230215141158.2426855-11-lersek at redhat.com > > The Notes section on each patch...

This is version 4 of the following sub-series: [libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe() [libnbd PATCH v3 10/29] lib/utils: add unit tests for async-signal-safe execvpe() http://mid.mail-archive.com/20230215141158.2426855-10-lersek at redhat.com http://mid.mail-archive.com/20230215141158.2426855-11-lersek at redhat.com The Notes section on each patch records the updates for that p...

...04:59AM +0100, Laszlo Ersek wrote: > On 3/20/23 20:41, Eric Blake wrote: > > On Sun, Mar 19, 2023 at 10:41:37AM +0100, Laszlo Ersek wrote: > >> This is version 4 of the following sub-series: > >> > >> [libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe() > >> [libnbd PATCH v3 10/29] lib/utils: add unit tests for async-signal-safe execvpe() > >> ... > > > > Series merged as commit range 742cbd8c7adc..0b7172b3cffa. I see you already fixed one pipeline failure due to some gcc versions being more picky about function...

...gt;> On 3/20/23 20:41, Eric Blake wrote: > >>> On Sun, Mar 19, 2023 at 10:41:37AM +0100, Laszlo Ersek wrote: > >>>> This is version 4 of the following sub-series: > >>>> > >>>> [libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe() > >>>> [libnbd PATCH v3 10/29] lib/utils: add unit tests for async-signal-safe execvpe() > >>>> > > ... > >>> > >> > >> Series merged as commit range 742cbd8c7adc..0b7172b3cffa. > > > > I see you already fixed one pipe...

...tprint, but it violates GNU Coding Standards (which state that in general, an application's behavior should not depend on argv[0], precisely so that renaming it doesn't change its behavior). > > So, no, this mess (= Alpine Linux) is not salvageable. The > "lib/test-fork-safe-execvpe.sh" script depends on "expr" being > functional under the name "f". And yes I want "f" to be a > single-character filename; otherwise the nice tabular formatting of the > script falls apart (or produces overlong lines). > > As last step, I learned...

...aszlo Ersek wrote: >> On 3/20/23 20:41, Eric Blake wrote: >>> On Sun, Mar 19, 2023 at 10:41:37AM +0100, Laszlo Ersek wrote: >>>> This is version 4 of the following sub-series: >>>> >>>> [libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe() >>>> [libnbd PATCH v3 10/29] lib/utils: add unit tests for async-signal-safe execvpe() >>>> > ... >>> >> >> Series merged as commit range 742cbd8c7adc..0b7172b3cffa. > > I see you already fixed one pipeline failure due to some gcc versions &g...

This is the error I receive when attempting to start the service. This is from /var/log/messages. Mar 27 11:41:17 portero smb: smbd startup succeeded Mar 27 11:41:17 portero smb: nmbd startup failed Mar 27 11:41:18 portero srvsvcd: execvp: No such file or directory Mar 27 11:41:18 portero smb: srvsvcd startup failed Mar 27 11:41:18 portero wkssvcd: execvp: No such file or directory Mar 27 11:41:18 portero smb: wkssvcd startup failed Mar 27 11:41:18 portero lsarpcd: execvp: No such file or directory Mar 27 11:41:18 portero smb: lsarp...

Per POSIX, execvp() is not safe to call in a child process forked from a multi-threaded process. We can now replace the execvp() call in the child process with a call to our fork-safe (async-signal-safe) variant. Prepare our internal execvpe context on the parent's construction path, use the context in the chil...

.../20/23 20:41, Eric Blake wrote: >>>>> On Sun, Mar 19, 2023 at 10:41:37AM +0100, Laszlo Ersek wrote: >>>>>> This is version 4 of the following sub-series: >>>>>> >>>>>> [libnbd PATCH v3 09/29] lib/utils: introduce async-signal-safe execvpe() >>>>>> [libnbd PATCH v3 10/29] lib/utils: add unit tests for async-signal-safe execvpe() >>>>>> >>> ... >>>>> >>>> >>>> Series merged as commit range 742cbd8c7adc..0b7172b3cffa. >>> >>> I see yo...

...mmit 6a032d81581978187f562e5533a32e0a6a3d352b (tag: cvs/libc-960210) > Author: Roland McGrath <roland at gnu.org> > Date: Sat Feb 10 10:00:27 1996 +0000 > > Sat Feb 10 04:18:48 1996 Roland McGrath <roland at churchy.gnu.ai.mit.edu> > > * posix/execvp.c: If execv fails with ENOEXEC, run the shell on > the file. > > Fri Feb 9 11:46:45 1996 Roland McGrath <roland at churchy.gnu.ai.mit.edu> > > * time/Makefile (CFLAGS-zdump.c, CFLAGS-zic.c, CFLAGS-ialloc.c, > CFLAGS-scheck...

...ation is here: > http://0pointer.de/blog/projects/socket-activation.html > --- > +++ b/generator/states-connect-socket-activation.c > +/* This is baked into the systemd socket activation API. */ > +#define FIRST_SOCKET_ACTIVATION_FD 3 > + > +/* Prepare environment for calling execvpe when doing systemd socket > + * activation. Takes the current environment and copies it. Removes > + * any existing LISTEN_PID or LISTEN_FDS and replaces them with new > + * variables. env[0] is "LISTEN_PID=..." which is filled in by > + * CONNECT_SA.START, and env[1] is &...

...> > standardizing realpath, so I've filed it: > > https://bugs.busybox.net/show_bug.cgi?id=15466 > > I've found another busybox bug. > > The "/bin/sh" utility is provided by busybox as well (via the usual symlinking). > > Per POSIX, if > > execvp(file, { argv[0], argv[1], ..., NULL }) > > were to fail with -1/ENOEXEC, then execvp() must retry "as if" with > > execv(<shell path>, { argv[0], file, argv[1], ..., NULL }) > > In other words, if direct execution of "file" failed because "file&...

...try to start the smbd server I get the following error. Please tell me where I am wrong. -------------------------------------------------------------------- [root@redhat lock]# /etc/rc.d/init.d/smb restart Restarting SMB services: Shutting down SMB services: [FAILED] Starting SMB services: execvp: Permission denied execvp: Permission denied [FAILED] [FAILED] done. -------------------------------------------------------------------- >>>Here is my smb.conf file -----------------------------...

On 2/21/23 20:32, Eric Blake wrote: > On Tue, Feb 21, 2023 at 07:07:38PM +0100, Laszlo Ersek wrote: >> Well, given Daniel's comments meanwhile, it seems like the original >> execvp() is something we shouldn't fret about. :/ > > glibc marks execvp() and exevpe() as 'MT-Safe env', which means it > does not modify 'environ' and presumably does not use 'malloc'. If > the only reason POSIX marks execvp() as thread-unsafe is because of >...

Hi everybody, I try to convert mbox to maildir using local locations /root/mail is a dir with mboxes /root/INBOX is mbox file h=/root dsync -f -v mirror \ mbox:$h/mail:INBOX=$h/INBOX \ maildir:$h/Maildir:CONTROL=$h/dovecot:INDEX=$h/dovecot \ as result I have dsync(root): Fatal: execvp(mbox:/root/mail:INBOX=/root/INBOX) failed: No such file or directory dsync-local(root): Error: read() from worker server failed: EOF thank you for any help FreeBSD, dovecot 2.0.15

On Wed, Feb 22, 2023 at 01:47:02AM +0100, Laszlo Ersek wrote: > On 2/21/23 20:32, Eric Blake wrote: > > On Tue, Feb 21, 2023 at 07:07:38PM +0100, Laszlo Ersek wrote: > > >> Well, given Daniel's comments meanwhile, it seems like the original > >> execvp() is something we shouldn't fret about. :/ > > > > glibc marks execvp() and exevpe() as 'MT-Safe env', which means it > > does not modify 'environ' and presumably does not use 'malloc'. If > > the only reason POSIX marks execvp() as thread-unsaf...