Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Dec 2014 10:32:24 +0000 (UTC)
From:      Laszlo Danielisz <laszlo.danielisz@yahoo.com>
To:        "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   Re: How to run a server at normal priority?
Message-ID:  <303350581.168208.1418812344298.JavaMail.yahoo@jws106144.mail.bf1.yahoo.com>
In-Reply-To: <54906D97.4090304@gmail.com>
References:  <54906D97.4090304@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
That is what I wanted to say, be carefully when you change the priority of =
a process, they have that specific priority for a reason.
Though, if you really want you my use renice:https://www.freebsd.org/cgi/ma=
n.cgi?query=3Drenice&sektion=3D8
renice command: Change the Priority of a Already Running Process
 =C2=A0=20

     On Tuesday, December 16, 2014 6:36 PM, Noel <noeldude@gmail.com> wrote=
:
  =20

 On 12/16/2014 11:13 AM, Unga via freebsd-questions wrote:
> Hi all
> I have FreeBSD 9.0 on a i386 hardware.
> I have few server daemons run on this machine, all runs at normal priorit=
y (20) except one at priority (52).
> All server daemons run as their respective user ID. How to run this low p=
riority server at normal priority as others?
> Many thanks in advance.
> Best regardsUnga=20

The developer chose that priority intentionally when they wrote the
program.=C2=A0 Consider carefully before you change it.

man renice



=C2=A0 -- Noel Jones
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org=
"


   
From owner-freebsd-questions@FreeBSD.ORG  Wed Dec 17 11:15:06 2014
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 299B71926;
 Wed, 17 Dec 2014 11:15:06 +0000 (UTC)
Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 9DF3181D;
 Wed, 17 Dec 2014 11:15:05 +0000 (UTC)
Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2])
 by bede.home.qeng-ho.org (8.14.7/8.14.7) with ESMTP id
 sBH9bEaQ014203; Wed, 17 Dec 2014 09:37:14 GMT
 (envelope-from freebsd@qeng-ho.org)
Message-ID: <54914ECA.9040300@qeng-ho.org>
Date: Wed, 17 Dec 2014 09:37:14 +0000
From: Arthur Chance <freebsd@qeng-ho.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: FreeBSD-Questions <freebsd-questions@freebsd.org>,
 security-officer@FreeBSD.org
Subject: Re: freebsd-update and boot environments clash - rm /  attempted!
References: <54914CCC.7080102@qeng-ho.org>
In-Reply-To: <54914CCC.7080102@qeng-ho.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 11:15:06 -0000

On 17/12/2014 09:28, Arthur Chance wrote:
> I just updated my systems to deal with the latest security bulletin. On
> the machines where I'm running zfs based boot environments I got the
> somewhat worrying:

A correction. It's not machines using boot environments, it's machines 
running 10.1-REL. (Most of my 10.1 boxes use b.e., the one that doesn't 
is very small and slow, so took a while to update.) The problem did not 
manifest on my one 10.0-REL box.


-- 
Those who do not learn from computing history are doomed to
GOTO 1



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?303350581.168208.1418812344298.JavaMail.yahoo>