Re: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

On 2017-Aug-30, at 4:32 PM, Don Lewis wrote: > On 30 Aug, Mark Millard wrote: >> On 2017-Aug-30, at 4:00 AM, Mark Linimon wrote: >> >>> On Wed, Aug 30, 2017 at 03:09:40AM -0700, Mark Millard wrote: It appears that qemu-ppc64-static and qemu-ppc-static from emulators/qemu-user-static

Re: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

On 30 Aug, Mark Millard wrote: > On 2017-Aug-30, at 4:00 AM, Mark Linimon wrote: > >> On Wed, Aug 30, 2017 at 03:09:40AM -0700, Mark Millard wrote: >>> It appears that qemu-ppc64-static and qemu-ppc-static from >>> emulators/qemu-user-static are broken. >> >> Correct, and

Re: pkg issue after FreeBSD 11 upgrade

Thank you for your support Baptiste, I really appreciate that. As same as HANDLE_RC_SCRIPTS option the new one should be handled carefully. Please keep us posted when it's ready. On Wednesday, August 30, 2017, Baptiste Daroussin wrote: > On Wed, Aug 30, 2017 at 10:07:51AM

Re: pkg issue after FreeBSD 11 upgrade

On Wed, Aug 30, 2017 at 10:07:51AM -0300, Cassiano Peixoto wrote: > Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal > with when I need to restart a service without upgrading? Reaper > functionnality is a trouble for many administrators who made meta ports to > manage their

Re: pkg issue after FreeBSD 11 upgrade

Cassiano Peixoto wrote: Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal with when I need to restart a service without upgrading? Reaper functionnality is a trouble for many administrators who made meta ports to manage their servers. I really think it could be a option to

Re: pkg issue after FreeBSD 11 upgrade

Hi Baptiste, > On 30. Aug 2017, at 3:05 PM, Baptiste Daroussin wrote: > >> No. At OPNsense we use a patch to revert the behaviour. >> >> https://github.com/opnsense/ports/blob/master/ports-mgmt/pkg/files/patch-libpkg_scripts.c > > Why and what is your use case, there is a

Re: pkg issue after FreeBSD 11 upgrade

Hi Franco, Thank you. You know what I'm suffering. As I said in my last email I think it would be an option to enable/disable. I just upgraded my customers servers to FreeBSD 11 and I just realized it. I think when more admins who maintain this kind of port (needing to restart services), as soon

Re: pkg issue after FreeBSD 11 upgrade

Ok I know about HANDLE_RC_SCRIPTS, it's a good approach. But how to deal with when I need to restart a service without upgrading? Reaper functionnality is a trouble for many administrators who made meta ports to manage their servers. I really think it could be a option to be enabled/disabled. Can

Re: pkg issue after FreeBSD 11 upgrade

On Wed, Aug 30, 2017 at 03:01:30PM +0200, Franco Fichtner wrote: > Hi Cassiano, > > > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto > > wrote: > > > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. > > It was a later 10.x change as far as I

Re: pkg issue after FreeBSD 11 upgrade

Hi Cassiano, > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto > wrote: > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. It was a later 10.x change as far as I know. > Is there some flag to disable it? Or some hack that I could do? No.

Re: pkg issue after FreeBSD 11 upgrade

On Wed, Aug 30, 2017 at 09:55:22AM -0300, Cassiano Peixoto wrote: > Hi Baptiste, > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. It only worked on FreeBSD 10 prior to 10.2, the reaper functionnality in freebsd kernel appeared in 10.2 > > Cron is just an example, I

Re: pkg issue after FreeBSD 11 upgrade

Hi Baptiste, Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. Cron is just an example, I manage more than 50 FreeBSD servers, and I've been using ports for years to update some configs and restart the service on all of them. Many times I need to change nginx config, ldap,

Re: pkg issue after FreeBSD 11 upgrade

On Wed, Aug 30, 2017 at 09:00:55AM -0300, Cassiano Peixoto wrote: > Hi Matthew, > > Sorry back to this subject. But I really need to restart services with a > port. I'm quite sure there is a bug with pkg and FreeBSD 11. > > I made a simple port to restart cron service: It is not a bug, it is by

Re: pkg issue after FreeBSD 11 upgrade

Try tracing the install with truss or ktrace. I suspect you'll find there is an issue where a pipe being closed; stdin, stdout or stderr, which results in the daemon that was started being stopped again, or something similar. On 30/08/2017 13:00, Cassiano Peixoto wrote: Hi Matthew, Sorry

Re: pkg issue after FreeBSD 11 upgrade

Hi Matthew, Sorry back to this subject. But I really need to restart services with a port. I'm quite sure there is a bug with pkg and FreeBSD 11. I made a simple port to restart cron service: # $FreeBSD$ PORTNAME= ze PORTVERSION=1.0 CATEGORIES= custom MASTER_SITES= # DISTFILES=

Re: FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

On Wed, Aug 30, 2017 at 03:09:40AM -0700, Mark Millard wrote: > It appears that qemu-ppc64-static and qemu-ppc-static from > emulators/qemu-user-static are broken. Correct, and known for some time. (fwiw sparc64 hangs as well.) mcl ___

Re: PR looking for committer

El 29 ago. 2017 21:36, "Kurt Jaeger" escribió: Hi! > Can a committer have a look at this? > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221835 It hit the tree, thanks! Thank you. Could you (or any other committer) also have a look at the PR blocked by this one? --

FYI: qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use with poudriere; qemu-arm-static and qemu-aarch64-static work

qemu-ppc64-static and qemu-ppc-static "live-hang" when I attempt use them with poudriere, hanging at the command (showing an example process id): /usr/local/bin/qemu-ppc-static /bin/ps -ww -p 47841 -o jid= which eats CPU time and grows memory SIZE over time. Examples from after waiting a while

FreeBSD ports you maintain which are out of date

Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated,