similar to: New install smbd does not run seen 1000 times on this ml

On 3/22/23 15:45, Laszlo Ersek wrote: > On 3/21/23 18:28, Eric Blake wrote: > >> it is indeed 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

On 3/21/23 18:28, Eric Blake wrote: > it is indeed 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 })

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

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

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 child, and release the context in the parent on the way out, regardless of whether the

I was going through the config.log after installing R successfully on a Linux ppc64 machine. However, I could not install the MCMCpack and looked at the config.log file for gcc and g++ errors.I found some of them and have pasted them below. Please let me know if they can affect the installation of other packages on R. ------------------ configure:7479: checking whether we are using the GNU

Use an extensible buffer (a vector<char>) when reading /proc/self/cmdline. Tidy up some error messages. --- plugins/vddk/reexec.c | 57 ++++++++++++++++++++++++++----------------- 1 file changed, 35 insertions(+), 22 deletions(-) diff --git a/plugins/vddk/reexec.c b/plugins/vddk/reexec.c index 5a5e9844..9641ee8c 100644 --- a/plugins/vddk/reexec.c +++ b/plugins/vddk/reexec.c @@ -48,6

I am responding to your post, listed below. I am having the same problem with GoldMine which I believe is written in much the same way as most clipper based applications. Did you ever resolve the issue? I just posted to the newsgroup but did not hear back yet. I pormise to post a summary should an answer show up. I'm running 2.2.1a and will soon move to 2.2.2 to avoid oplock problem.

We're trying to build OpenSSH 3.0.2p1 for Solaris 8 (among others) and are running into a problem with UseLogin and utmpx. If we set "UseLogin no" then we can login okay. finger or who won't find us, even with a TTY allocated altough "who /etc/wtmpx" will find us. But the real problem is if we set "UseLogin true" which we must do for BSM support on some

http://bugzilla.mindrot.org/show_bug.cgi?id=1150 Summary: sshd records incorrect login times Product: Portable OpenSSH Version: 4.3p1 Platform: Other URL: http://marc.theaimsgroup.com/?l=openssh-unix- dev&m=113890107022083&w=2 OS/Version: Solaris Status: NEW Severity: major

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

On Wed, Mar 22, 2023 at 03:45:17PM +0100, Laszlo Ersek wrote: > On 3/21/23 18:28, Eric Blake wrote: > > > it is indeed 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

Hello, (Samba 3.0.21c / Linux 2.4.27) a smbd process was hanging on a file server since one day. This smbd process was locking some files on the server, and that was causing some share violation for a Windows user (well, that what I think). I did a lsof on the smbd process, and I saw that the TCP netbios-ssn connection was still seen as established with the machine of the windows user that

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

Hello All, I had a problem with 2.0.3 on RH6.0 (linux) where a mount of an NT server share on my linux machine would mysteriously die after a period of time (a long time? not being used? don't know why, but hours of unuse). I would get an "input/output error" when I tried to do a df later. To get around the problem, I found I needed to "umount" (not smbumount) the

http://bugzilla.mindrot.org/show_bug.cgi?id=759 Summary: If sshd was started without explicit pathname, it dies when restarted Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo:

Hello Shorewall gurus, I have a dilemma with a public server. I want to migrate the current public server over to a new machine behind the current server''s firewall (shorewall 1.4). I have included a diagram below to help explain the target network I am working toward. I have read the shorewall online documentation and though I have used Shorewall the past 4 years in the current

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://marc.theaimsgroup.com/?l=openbsd-misc&m=106375452423794&w=2 http://marc.theaimsgroup.com/?l=openbsd-misc&m=106375456923804&w=2 Does this affect FreeBSD? - -Justin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/Z7QbdYQBw9Ox1VgRAsb2AJ0eZxI/s3Q5KJQxvgROLM8FnU1kiQCfSsma XcJ/R/6s9yQJwBTYDeWI2+Y= =BoVH

Hello, I like to install Update my server but after the last update I have this Error System centos 7.7 when I Install "sieve" I have this error Mar 9 11:51:47 mx02 dovecot: master: Warning: Corrected permissions for login directory /var/run/dovecot/token-login Mar 9 11:51:47 mx02 dovecot: master: Dovecot v2.3.10 (0da0eff44) starting up for imap, lmtp, sieve (core dumps disabled)

http://bugzilla.mindrot.org/show_bug.cgi?id=1155 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #5 from dtucker at zip.com.au 2006-09-25 18:24 ------- For the record, I believe all of the outstanding