1- I tried to install 96 on one of my machines (via running pliant/fullpliant)but after I provide the user ID and password (at the os command line) the process is killed.2- On the same machine (which used to host a pliant HTTP server running version84), when I try to install version 84, via a linux script called pliantServer, which contains thecommand

About release 84, il you are running a new Linux kernel (2.6.12 or later)then Pliant precompiling will not work because of the poor randomisation ofthe addresse space introduced in Linux kernel to make virus life harder (*)

About release 96, if you have problems with it, you can just stay withrelease 95 at the moment. I published release 96 just in order to makea proper milestone before introducing the storage subsystem.

If you have problems when running: /pliant/fullpliantYou can try instead: pliant reset module /pliant/install/precompile.pli module /pliant/fullpliant/run.pliwhich is the same, but can be extended to: pliant debug 2 reset module /pliant/install/precompile.pli module /pliant/fullpliant/run.pliin order to run more internal tests.With luck, it could provide you more meaningfull messages.

(*) Basically, the memory address I get when calling 'mmap' on one run is not granted to be allowed to request on the next run. This is the result of a poor implementation of randomisation in the Linux kernel, but since Linux kernel is a large project and Pliant is not much used, the official slogan about free softwares that 'bugs get fixed' does not apply :-(

Message posted by marcus on2006/03/14 21:34:59

So we (I) will have a problem to keep the Pliant documentation initiative siterunning. Because, as you recall, Patrice's documentation tools only work onp-84; but my server here at school has been upgraded (for security reasons, Ithink) to a newer Linux kernel.

It is unlikely I will be able to go back to the old kernel.

Any suggestions?

ps: on a unrelated note, I just bought my first Macs: an iMac and the MacBook Pro, both with the Intel core duo. I'm loving them. Too bad Pliant does run on them... :(

Message posted by hubert.tonneau on2006/03/14 21:48:28

So the question is: why does Patrice tool refuse to work on newer Pliantreleases ?

Message posted by pom on2006/03/14 21:53:57

I don't refuse. I don't know how to make the same meta...

Message posted by hubert.tonneau on2006/03/14 21:55:32

Can you remind me where the problem is with changes in the meta engine ?I just don't remember.

Message posted by marcus on2006/03/14 21:57:12

Regarding the problem of my server being killed during start up, it also happenswith release 95.

Here is the output:.....WELCOME TO FULLPLIANT

You need an account to be able to connect to your Pliant HTTPserver through your favorite browser.User ID: rootPassword: .......

Killeding HTTP server. Please wait ...[root@playground ~]#

Incidentally, my system admin has just upgraded my machine to linux kernel 2.6.9-34.

Message posted by pom on2006/03/14 22:00:50

The problem was in the meta "sample", which took a bloc of source codeand should do two things: first compile and register the page (or the module)corresponding to the bloc, second pretty print int on the page. A button"execute" then was used to run the sample.The idea behind was that the documentation of the basics could involveup to 50 samples in a .page which are all about 3 lines long. Writinga separate file for each sample seemed unpracticable.

Actually, the best would be to be able to put the samples in the database, butit might be even harder...

Also if the Pliant process crashes with absolutely no message, then just try:pliant verbose 2 debug 2 reset module /pliant/install/precompile.pli module /pliant/fullpliant/run.pli

Message posted by pom on2006/03/14 22:04:38

Are you sure you did not forget to delete all your .dump ?

Message posted by hubert.tonneau on2006/03/14 22:07:50

> The problem was in the meta "sample", which took a bloc of source code> and should do two things: first compile and register the page (or the module)> corresponding to the bloc, second pretty print int on the page.

I thought 'do_compile_dynamic_page' method in /pliant/protocol/http/server.pliwas introduced to let you do that.So what problem remains ?

Message posted by hubert.tonneau on2006/03/14 22:15:29

Patrice is right:each time somebody modifies your Linux configuration (kernel, libraries) youmay need to delete the Pliant .dump files because the address space layoutwill be modified, even if you don't change of Pliant release.

Message posted by maybe Marcus on2006/03/15 01:06:33

The problem persists, even after deleting the dump file.

I've run the command suggested by Hubert. Below is the last line of the (humongous) output before the process is killed:

parse /pliant/linux/kernel/statistics.pli (internals) 151 4

Message posted by hubert.tonneau on2006/03/15 01:35:54

I prepose you the following protocol:

1) type in 'pliant' with no extra agument in order to check that the right executable is executed (see release number in the output)

2) check that no Unix right problem prevented the Pliant tarball to properly extract, and the the Unix user you use when running Pliant has proper rights on the various parts of Pliant

3) move asside the /pliant_security and /pliant_data directories to see if a fresh configuration works, and if it does, try puting back some files until you find the disturbing one

Message posted by maybe Marcus on2006/03/15 03:55:49

> 1) ...

The release number is correct.

> 2) check that no Unix right problem prevented the Pliant tarball to properly> extract, and the the Unix user you use when running Pliant has proper rights> on the various parts of Pliant

That, I believe, is where the problem resides.

I am running the thing as root. When I untar the ball, the group/user seemodd: