From: teigland@sourceware.org <teigland@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] cluster/group/daemon main.c
Date: 15 Nov 2006 14:35:06 -0000 [thread overview]
Message-ID: <20061115143506.6350.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: cluster
Changes by: teigland at sourceware.org 2006-11-15 14:35:05
Modified files:
group/daemon : main.c
Log message:
fix sched_priority from sdake
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/group/daemon/main.c.diff?cvsroot=cluster&r1=1.52&r2=1.53
--- cluster/group/daemon/main.c 2006/11/09 15:47:29 1.52
+++ cluster/group/daemon/main.c 2006/11/15 14:35:05 1.53
@@ -136,6 +136,8 @@
char *argv[4];
int status, rv = 0;
+ /* FIXME: ignore gfs/gfs2 nolock fs's */
+
rv += kernel_instance_count("/sys/kernel/dlm");
rv += kernel_instance_count("/sys/fs/gfs");
rv += kernel_instance_count("/sys/fs/gfs2");
@@ -907,7 +909,7 @@
rv = sched_get_priority_max(SCHED_RR);
if (rv != -1) {
- sched_param.sched_priority = 2;
+ sched_param.sched_priority = rv;
rv = sched_setscheduler(0, SCHED_RR, &sched_param);
if (rv == -1)
log_print("could not set SCHED_RR priority %d err %d",
next reply other threads:[~2006-11-15 14:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 14:35 teigland [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-01-11 17:59 [Cluster-devel] cluster/group/daemon main.c teigland
2007-01-11 17:59 teigland
2006-12-13 19:05 teigland
2006-12-13 19:05 teigland
2006-12-13 19:04 teigland
2006-12-01 15:25 teigland
2006-12-01 15:25 teigland
2006-12-01 15:24 teigland
2006-11-20 22:44 rpeterso
2006-11-17 16:28 teigland
2006-11-17 16:26 teigland
2006-10-24 17:08 teigland
2006-10-20 15:42 rpeterso
2006-09-14 20:49 teigland
2006-07-13 18:21 teigland
2006-06-22 19:06 teigland
2006-06-20 20:27 teigland
2006-06-14 21:38 teigland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061115143506.6350.qmail@sourceware.org \
--to=teigland@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).