Problem compiling runit

Problem compiling runit

[Nandakumar, R (Raja)]

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

Re: Problem compiling runit

[Gerrit Pape]

On Tue, May 30, 2006 at 10:47:18AM +0100, Nandakumar, R (Raja) wrote:
> 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

> [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...

It's the program selftest that fails.  After compiling the programs, the
runit installation process runs selftests on the programs to check
whether they behave correctly.  On your system the selftest for the
chpst program fails.

> 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

chpst has two command line options -l, -L for file locking, both fail
for you.  It's the flock() or lockf() system call that returns ENOLCK on
your system, that means something like 'The kernel ran out of memory for
allocating lock records', check the man pages.  Check compile/sysdeps to
find out whether runit found flock() or lockf() on your system.

Regards, Gerrit.

Use of /var/service

[Nandakumar, R (Raja)]

Hi,

How important is the directory (what does it do?) /var/service for
runit?

Thanks a lot and Best Regards,
Raja.

Re: Use of /var/service

[Alex Efros]

Hi!

On Sun, Jun 25, 2006 at 10:55:10PM +0100, Nandakumar, R (Raja) wrote:
> How important is the directory (what does it do?) /var/service for
> runit?

Hahahaha. :)
We should do something with this.
This question posted in list again and again and again...
I think there two possible solutions:
1) setup auto-reply robot which will reply on every message with
   substring "/var/service"
2) move /var/service symlink into some dark, hidden place where nobody
   will find it to ask this question
:)

P.S. Nandakumar, check runit's website, there a lot of documentation which
describe /var/service function.

-- 
			WBR, Alex.