head	1.18;
access;
symbols;
locks
	nobody:1.18; strict;
comment	@# @;


1.18
date	99.09.24.01.36.40;	author nobody;	state Exp;
branches;
next	1.17;

1.17
date	99.09.23.21.30.25;	author nobody;	state Exp;
branches;
next	1.16;

1.16
date	99.09.23.04.15.04;	author nobody;	state Exp;
branches;
next	1.15;

1.15
date	99.09.23.04.04.25;	author nobody;	state Exp;
branches;
next	1.14;

1.14
date	99.09.23.04.02.13;	author nobody;	state Exp;
branches;
next	1.13;

1.13
date	99.09.23.04.01.27;	author nobody;	state Exp;
branches;
next	1.12;

1.12
date	99.09.23.03.58.07;	author nobody;	state Exp;
branches;
next	1.11;

1.11
date	99.09.23.03.57.34;	author nobody;	state Exp;
branches;
next	1.10;

1.10
date	99.09.23.03.55.40;	author nobody;	state Exp;
branches;
next	1.9;

1.9
date	99.09.23.03.52.59;	author nobody;	state Exp;
branches;
next	1.8;

1.8
date	99.09.23.03.48.48;	author nobody;	state Exp;
branches;
next	1.7;

1.7
date	99.09.23.03.48.11;	author nobody;	state Exp;
branches;
next	1.6;

1.6
date	99.09.23.03.46.29;	author nobody;	state Exp;
branches;
next	1.5;

1.5
date	99.09.23.03.41.43;	author nobody;	state Exp;
branches;
next	1.4;

1.4
date	99.09.23.03.39.26;	author nobody;	state Exp;
branches;
next	1.3;

1.3
date	99.09.23.03.25.37;	author nobody;	state Exp;
branches;
next	1.2;

1.2
date	99.09.23.03.24.43;	author nobody;	state Exp;
branches;
next	1.1;

1.1
date	99.09.23.03.24.37;	author nobody;	state Exp;
branches;
next	;


desc
@null
@


1.18
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 2
IDependOn-Set: 304
IDependOn-Set: 34
IDependOn-Set: 7
IDependOn-Set: 89
LastModifiedSecs: 938136997
Parent: 34
SequenceNumber: 16
Title: How do I manipulate the JServ shared memory file?
Part: 0
Author-Set: mark@@i-drive.com
LastModifiedSecs: 938136997
Type: html
Lines: 12
The shared memory file can be read easily from shell, perl, or C applications. One way to determine the current status of currently routed VMs would be with the UNIX strings command. Remove unwanted characters with sed. Use grep to grab the  pertinent lines. The result could be something like so:

<br><br>
strings /var/log/jserv_shm | sed -e 's/\$//g' -e 's/-$//' | grep -e '[-+/X]'
<br><br>
Here is a tool for manipulating the JServ shared memory file. This makes possible a  managed removal (or re-addition) of VM's from the load balancing list by updating the STATUS on the given VM from [+-/X] to whatever new state you wish. This makes for smoother live content updates when you are load balancing between many VMs (Refer to Jean-Luc Rochet's documentation for a better description of the single character states<a href="http://jserv.apache.org/jserv/howto.load-balancing.html#Internalstate - Admistration tasks"> here</a>).
<br><br>
<a href="http://www.idrive.com/mark/Jserv/shm-update.sh.txt">shm-update.sh</a>
<br><br>
And here is a less robust perl version:<br>
<a href="http://www.idrive.com/mark/Jserv/shm-update.pl.txt">shm-update.pl</a>
<br><br>
EndPart: 0
@


1.17
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938122223
d9 1
a9 1
SequenceNumber: 15
d13 1
a13 1
LastModifiedSecs: 938122223
d16 1
a16 1
The shared memory file can be read easily from shell, perl, or C applications. One way to determine the current status of the routed VMs would be with the UNIX strings command. Remove unwanted characters with sed. Use grep to grab the  pertinent lines. The result could be something like so:
@


1.16
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938060104
d9 1
a9 1
SequenceNumber: 14
d13 1
a13 1
LastModifiedSecs: 938060104
d15 1
a15 1
Lines: 9
d24 3
@


1.15
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938059465
d9 1
a9 1
SequenceNumber: 13
d13 1
a13 1
LastModifiedSecs: 938059465
d21 1
a21 1
Here is a tool for manipulating the JServ shared memory file. This makes possible a  managed removal (or re-addition) of VM's from the load balancing list by updating the STATUS on the given VM from [+-/X] to whatever new state you wish. This makes for smoother live update capability if you are load balancing between many VMs (Refer to Jean-Luc Rochet's documentation for a better description ofthe single character states<a href="http://jserv.apache.org/jserv/howto.load-balancing.html#Internalstate - Admistration tasks"> here</a>).
@


1.14
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938059333
d9 1
a9 1
SequenceNumber: 12
d13 1
a13 1
LastModifiedSecs: 938059333
d21 1
a21 1
Here is a tool for manipulating the JServ shared memory file. This makes possible a  managed removal (or re-addition) of VM's from the load balancing list by updating the STATUS on the given VM from [+-/X] to whatever new state you wish. This makes for smoother live update capability if you are load balancing between many VMs (Refer to Jean-Luc Rochet's documentation for a better description ofthe single character states<a href="http://jserv.apache.org/jserv/howto.load-balancing.html"> here</a>).
@


1.13
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938059286
d9 1
a9 1
SequenceNumber: 11
d13 1
a13 1
LastModifiedSecs: 938059286
d15 1
a15 1
Lines: 12
d21 1
a21 3
Here is a tool for manipulating the JServ shared memory file. This makes possible a  managed removal (or re-addition) of VM's from the load balancing list by updating the STATUS on the given VM from [+-/X] to whatever new state you wish. This makes for smoother live update capability if you are load balancing between 
many VMs (Refer to Jean-Luc Rochet's documentation for a better description of
the single character states<a href="http://jserv.apache.org/jserv/howto.load-balancing.html"> here</a>).
a22 1

d24 1
a24 1

@


1.12
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938059086
d9 1
a9 1
SequenceNumber: 10
d13 1
a13 1
LastModifiedSecs: 938059086
d23 1
a23 1
the single character states http://jserv.apache.org/jserv/howto.load-balancing.html).
d25 2
a26 2
shm-update.sh:
http://www.idrive.com/mark/Jserv/shm-update.sh.txt
@


1.11
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938059053
d9 1
a9 1
SequenceNumber: 9
d13 1
a13 1
LastModifiedSecs: 938059053
d18 1
a18 1
<br>
d20 1
a20 1
<br>
d24 1
a24 1
<br>
@


1.10
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938058940
d9 1
a9 1
SequenceNumber: 8
d13 1
a13 1
LastModifiedSecs: 938058940
d15 2
a16 2
Lines: 11
The shared memory file can be read easily from shell, perl, or C applications.<br> One way to determine the current status of the routed VMs would be with the UNIX <br>strings command. Remove unwanted characters with sed. Use grep to grab the <br> pertinent lines. The result could be something like so:
d18 1
d20 3
a22 3

Here is a tool for manipulating the JServ shared memory file. This enables a <br> managed removal (or re-addition) of VM's from the load balancing list by<br> updating the STATUS on the given VM from [+-/X] to whatever new state you wish.<br> This makes for smoother live update capability if you are load balancing between <br>
many VMs (Refer to Jean-Luc Rochet's documentation for a better description of<br>
d24 1
a24 1

@


1.9
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938058779
d9 1
a9 1
SequenceNumber: 7
d13 4
a16 3
LastModifiedSecs: 938058779
Lines: 10
The shared memory file can be read easily from shell, perl, or C applications. One way to determine the current status of the routed VMs would be with the UNIX strings command. Remove unwanted characters with sed. Use grep to grab the pertinent lines. The result could be something like so:
d20 3
a22 2
Here is a tool for manipulating the JServ shared memory file. This enables a managed removal (or re-addition) of VM's from the load balancing list by updating the STATUS on the given VM from [+-/X] to whatever new state you wish. This makes for smoother live update capability if you are load balancing between 
many VMs (Refer to Jean-Luc Rochet's documentation for a better description of the single character states http://jserv.apache.org/jserv/howto.load-balancing.html).
@


1.8
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938058528
d9 1
a9 1
SequenceNumber: 6
d13 1
a13 1
LastModifiedSecs: 938058528
d15 1
a15 1
The shared memory file can be read easily from shell, perl, or C applications. One way to determine the current status of the routed VMs would be with the UNIX strings command. Remove unwanted characters with sed. Add a grep to filter out the pertinent lines. The result could be something like so:
d17 1
a17 1
strings /var/log/jserv_shm | sed -e 's/\$-*//g' | grep -e '[-+/X]'
@


1.7
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938058490
d9 1
a9 1
SequenceNumber: 5
d13 1
a13 1
LastModifiedSecs: 938058490
d22 2
a23 2
shm-pdate.sh:
http://www.idrive.com/mark/Jserv/shm-update.sh.txt">
@


1.6
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938058389
d9 1
a9 1
SequenceNumber: 4
d13 2
a14 2
LastModifiedSecs: 938058389
Lines: 9
d20 1
a20 1
many VMs (Refer to Jean-Luc Rochet's documentation for a better description of the single character states http://jserv.apache.org/jserv/howto.load-balancing.html):
d22 2
a23 1
<a href="http://www.idrive.com/mark/Jserv/shm-update.sh.txt">shm-update.sh.txt</a>
@


1.5
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938058103
d9 1
a9 1
SequenceNumber: 3
d13 3
a15 4
LastModifiedSecs: 938058103
Lines: 10

The shared memory file can be read easily from shell, perl, or C applications. One way to determine what the current status of the routed VMs would be with the UNIX strings command. Remove unwanted characters with sed. Add a grep to filter out the pertinent lines. The result could be something like so:
d19 2
a20 2
Here is a tool for manipulating the JServ shared memory file. This enables a managed removal (or re-addition) of VM's from the load balancing list by updating the STATUS on the given VM from [+-/X] to whatever new state you wish. This makes for a smoother live update mechanism when load balancing between 
many VMs.
@


1.4
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938057965
d9 1
a9 1
SequenceNumber: 2
d13 2
a14 4
LastModifiedSecs: 938057965
Type: html
Lines: 11
<PRE>
d24 1
a24 1
</PRE>
@


1.3
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938057136
d9 1
a9 1
SequenceNumber: 1
d11 17
@


1.2
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938057077
d9 2
a10 2
SequenceNumber: 0
Title: New Item
@


1.1
log
@null
@
text
@d6 1
@
