supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Nandakumar, R \(Raja\)" <R.Nandakumar@rl.ac.uk>
Subject: Problem compiling runit
Date: Tue, 30 May 2006 10:47:18 +0100	[thread overview]
Message-ID: <7231C15EAC2F164CA6DC326D97493C8B01C1DE4A@exchange35.fed.cclrc.ac.uk> (raw)

Hi,

When I try to compile on my linux machine, I get the problem given
below. Could someone help. I am trying this on a GNU/Linux with kernel
version 2.4.21-20.EL+MA

Thanks,
Raja.

[blabl@bla runit-1.5.1]$ ./package/install
Linking ./src/* into ./compile...
Compiling everything in ./compile...
+ cd compile
+ exec make
make: Nothing to be done for `default'.
Copying commands into ./command...
Checking commands in ./command...
+ cd compile
+ exec make check
./check-local chpst runit runit-init runsv runsvchdir runsvdir sv svlogd
utmpset
Checking chpst...
usage: chpst [-vP012] [-u user[:group]] [-U user[:group]] [-e dir] [-/
root] [-n nice] [-l|-L lock] [-m n] [-d n] [-o n] [-p n] [-f n] [-c n]
prog

100
$Id: chpst.c,v 1.10 2006/03/04 17:11:20 pape Exp $
usage: chpst [-vP012] [-u user[:group]] [-U user[:group]] [-e dir] [-/
root] [-n nice] [-l|-L lock] [-m n] [-d n] [-o n] [-p n] [-f n] [-c n]
prog

100
test=1
0
chpst: fatal: unable to lock:
/distribution/admin/runit-1.5.1/compile/check-tmp: no locks available
111
chpst: fatal: unable to lock:
/distribution/admin/runit-1.5.1/compile/check-tmp: no locks available
111
0
0
chpst failed.
make: *** [check] Error 1


             reply	other threads:[~2006-05-30  9:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-30  9:47 Nandakumar, R (Raja) [this message]
2006-05-30 11:42 ` Gerrit Pape
2006-06-25 21:55   ` Use of /var/service Nandakumar, R (Raja)
2006-06-26  1:41     ` Alex Efros

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=7231C15EAC2F164CA6DC326D97493C8B01C1DE4A@exchange35.fed.cclrc.ac.uk \
    --to=r.nandakumar@rl.ac.uk \
    /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).