aboutsummaryrefslogtreecommitdiff
path: root/pipermail/nel/2001-February/000285.html
blob: 3f6cbc09ef4ba5dd38489f9fc724b795bcf06cfb (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
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:
&gt;<i>     Most of my 'fixes' aren't really, they address the symptoms rather
</I>&gt;<i>     than the cause, though I don't think I've broken anything major 
</I>&gt;<i>     with them ;) If anyone wants to give me some hints on what could
</I>&gt;<i>     be causing them, please do. 
</I>
Well, we don't have hints, because, as you may surmise, these do not
occur here.

&gt;<i>           I gather the point of the Callback function is so that the 
</I>&gt;<i>           client which has loaded the Config file can become aware 
</I>&gt;<i>           of any changes to the parameters in the file, the time_service
</I>&gt;<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.

&gt;<i>         the client was exiting with a message in the logfile about 
</I>&gt;<i>           being unable to load file &quot;data/&quot;. Managed to eventually track
</I>&gt;<i>           it down to some of the texture loading code in 
</I>&gt;<i>           code/nel/src/3d/landscape.cpp. The loading of the diffuse
</I>&gt;<i>           texturemap doesn't do a check for textName == &quot;&quot; though
</I>&gt;<i>           the loading of the alpha texture map does. Haven't worked 
</I>&gt;<i>           out yet why it's decided that the textName is &quot;&quot; (it's too
</I>&gt;<i>           late ;)). I modified the code to do a test for textName == &quot;&quot;
</I>&gt;<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.

&gt;<i>     As some other comments - processes are defaulting under linux to
</I>&gt;<i>     some (IMHO) really ugly behaviour of 'fork'ing another process,
</I>&gt;<i>     the sole purpose of this appears to be to let them run in the 
</I>&gt;<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.

&gt;<i>     since it can be quite easily achieved by 'nohup'ing it and 
</I>&gt;<i>     shoving an '&amp;' on the end of the line. Am I missing something?
</I>
You could too, but you'd have to slide in a &quot;reasonable&quot; sleep N in
the shell startup script. With reasonable varying a lot.

&gt;<i>     (It makes it a bugger to debug, I can't run 'strace' on them effectively
</I>&gt;<i>     etc etc. Obviously, i just commented the code out of my version ;)
</I>&gt;<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>