diff options
| author | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
|---|---|---|
| committer | neodarz <neodarz@neodarz.net> | 2018-08-11 20:21:34 +0200 |
| commit | 0ea5fc66924303d1bf73ba283a383e2aadee02f2 (patch) | |
| tree | 2568e71a7ccc44ec23b8bb3f0ff97fb6bf2ed709 /pipermail/nel/2001-February/000285.html | |
| download | nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.tar.xz nevrax-website-self-hostable-0ea5fc66924303d1bf73ba283a383e2aadee02f2.zip | |
Initial commit
Diffstat (limited to 'pipermail/nel/2001-February/000285.html')
| -rw-r--r-- | pipermail/nel/2001-February/000285.html | 118 |
1 files changed, 118 insertions, 0 deletions
diff --git a/pipermail/nel/2001-February/000285.html b/pipermail/nel/2001-February/000285.html new file mode 100644 index 00000000..3f6cbc09 --- /dev/null +++ b/pipermail/nel/2001-February/000285.html @@ -0,0 +1,118 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Nel] Getting NeL up and running.</TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:archer%40nevrax.com"> + <LINK REL="Previous" HREF="000281.html"> + <LINK REL="Next" HREF="000271.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Nel] Getting NeL up and running.</H1> + <B>Vincent Archer</B> + <A HREF="mailto:archer%40nevrax.com" + TITLE="[Nel] Getting NeL up and running.">archer@nevrax.com</A><BR> + <I>Tue, 27 Feb 2001 18:00:05 +0100</I> + <P><UL> + <LI> Previous message: <A HREF="000281.html">[Nel] Getting NeL up and running.</A></li> + <LI> Next message: <A HREF="000271.html">[Nel] Some screen shots</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#285">[ date ]</a> + <a href="thread.html#285">[ thread ]</a> + <a href="subject.html#285">[ subject ]</a> + <a href="author.html#285">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE>According to Leighton Haynes: +><i> Most of my 'fixes' aren't really, they address the symptoms rather +</I>><i> than the cause, though I don't think I've broken anything major +</I>><i> with them ;) If anyone wants to give me some hints on what could +</I>><i> be causing them, please do. +</I> +Well, we don't have hints, because, as you may surmise, these do not +occur here. + +><i> I gather the point of the Callback function is so that the +</I>><i> client which has loaded the Config file can become aware +</I>><i> of any changes to the parameters in the file, the time_service +</I>><i> doesn't appear to set any callbacks for this though. *shrug* +</I> +That's exactly what it's supposed to be, yes. So, either the callbacks +are set incorrectly, or they are called while they should not be. + +><i> the client was exiting with a message in the logfile about +</I>><i> being unable to load file "data/". Managed to eventually track +</I>><i> it down to some of the texture loading code in +</I>><i> code/nel/src/3d/landscape.cpp. The loading of the diffuse +</I>><i> texturemap doesn't do a check for textName == "" though +</I>><i> the loading of the alpha texture map does. Haven't worked +</I>><i> out yet why it's decided that the textName is "" (it's too +</I>><i> late ;)). I modified the code to do a test for textName == "" +</I>><i> and made it default to loading the CTextureCross texture. +</I> +That's the strange part. It should not be loading an empty file name +at all. I suppose the check doesn't hurt either, so we'll look at +integrating it in future commits. + +><i> As some other comments - processes are defaulting under linux to +</I>><i> some (IMHO) really ugly behaviour of 'fork'ing another process, +</I>><i> the sole purpose of this appears to be to let them run in the +</I>><i> background. I don't see any really good reason for doing this, +</I> +Well, there is one. Basically, if you look at these processes, you'll +see they first do a set of initialisations, then fork. The whole +fork-and-exit sequence is used to guarantee that service N+1 isn't +started before service N has at least performed the minimum required +initialisations. + +><i> since it can be quite easily achieved by 'nohup'ing it and +</I>><i> shoving an '&' on the end of the line. Am I missing something? +</I> +You could too, but you'd have to slide in a "reasonable" sleep N in +the shell startup script. With reasonable varying a lot. + +><i> (It makes it a bugger to debug, I can't run 'strace' on them effectively +</I>><i> etc etc. Obviously, i just commented the code out of my version ;) +</I>><i> Perhaps a commandline switch would be more appropriate?) +</I> +That'll be added, yes. + +-- +Vincent Archer Email: <A HREF="mailto:archer@nevrax.com">archer@nevrax.com</A> + +Nevrax France. Off on the yellow brick road we go! + +</pre> + + + + + + + + + + + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI> Previous message: <A HREF="000281.html">[Nel] Getting NeL up and running.</A></li> + <LI> Next message: <A HREF="000271.html">[Nel] Some screen shots</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#285">[ date ]</a> + <a href="thread.html#285">[ thread ]</a> + <a href="subject.html#285">[ subject ]</a> + <a href="author.html#285">[ author ]</a> + </LI> + </UL> +</body></html> |