03-09-2007
9 More Discussions You Might Find Interesting
1. IP Networking
Hello friends I'm running Redhat 9.0 with linux kernel 2.4.20-8 & have iptables version 1.2.7a & encountering a problem that I narrate down.
I need to apply patch to my iptable and netfilter for connection tracking and load balancing that are available in patch-o-matic distribution by netfilter.... (0 Replies)
Discussion started by: Rakesh Ranjan
0 Replies
2. Solaris
I have several servers that are outside the country and are running Solaris 6 mainly with a few Solaris 7 boxes here and there. Because of that, we need to schedule time to change the time on March 11th and again in April, October and November. At least until the customer decides it's time to... (3 Replies)
Discussion started by: BOFH
3 Replies
3. SCO
I checked SCO's site for DST fix for SCO 5.0.0 and there iis not one available. Can I run a script in the cron to read in and change the time?
TiA (2 Replies)
Discussion started by: tbgeek
2 Replies
4. SCO
Hello,
Anyone know where I can find the DST updates for SCO Xdesktop 3.6.3?
Thanks (0 Replies)
Discussion started by: ddzc
0 Replies
5. AIX
Just a quick last minute thing here.
AIX 5.1. I ran the perl script referenced in the tutorials and found the AIX box is triggering DST on the 14th instead of the 11th. The 5.2 boxes come back with the right answers. The DST patches have been applied (or I'd have Apr 1st instead of the 14th).
... (0 Replies)
Discussion started by: BOFH
0 Replies
6. What is on Your Mind?
We have been discussing the 2007 changes to DST (Daylight Saving Time) for some time now. We hope that everything went well. But did it? Let us know by voting or by posting your experiences here. The poll will automatically close in 45 days. (6 Replies)
Discussion started by: Perderabo
6 Replies
7. AIX
Hello.
Our application is running on AIX box located in NSW , Australia. As DST starts on Oct 28th - Do you know IF AIX boxes have auto updates of day light saving times? IF not , how to do it? IF yes, where can I verify it?
Thank you! (3 Replies)
Discussion started by: panchpan
3 Replies
8. Linux
Hello,
I have linux server which is one hour behind after the DST change last week. I post some information below on the settings. any helpwould be helpful since I am newbie..
$ clock
Tue 04 Nov 2008 03:12:26 PM EST -0.785549 seconds
$more clock
Tue 04 Nov 2008 03:12:26 PM EST... (2 Replies)
Discussion started by: jbdavis02@yahoo
2 Replies
9. UNIX for Advanced & Expert Users
Hi,
I have one confusion regarding DST chnages which are going to happen after October. :confused: :confused:
I have few jobs on Autosys which run as per Japan Time. they shoudl not be affected by switiching off of DST time.
Our autosys instance server is based on UK which is running on... (0 Replies)
Discussion started by: girdharsourabh
0 Replies
LEARN ABOUT MOJAVE
shape_patch
SHAPE_PATCH(1) General Commands Manual SHAPE_PATCH(1)
NAME
shape_patch - shapeTools RMS generate patch file
SYNOPSIS
shape patch OLDRELEASE=<name1> NEWRELEASE=<name2> [PATCHFILE=<filename>]
DESCRIPTION
Shape patch generates a patch file for updating $(OLDRELEASE) to $(NEWRELEASE). Both releases are identified by release names associated
with the macros OLD-/NEWRELEASE on the command line. Valid release names are those generated by any of the shape_RMS (pre-)release building
procedures (see shape_releas(1)). Performing 'vl -all' with the release identification file as argument usually gives a good overview of
existing release names. Patch generation happens recursively over all subsystems being part of the current node. Hence, triggering shape
patch from the top node of the central source repository creates a patch file for the whole system.
The output of shape patch is stored in a file named <name1>+2+<name2>.pat. When the PATCHFILE macro is set on the command line, $(PATCH-
FILE) is taken as output file name instead. Defining PATCHFILE=- on the command line causes the patch to be written to standard output.
Note: For patches invoking multiple subsystems, $(PATCHFILE) should be set to an absolute pathname. If not, the patch generation procedure
will leave an equally named patch file for each visited subsystem.
The patch is constructed using the vdiff(1) command and can be applied to any installation of $(OLDRELEASE) by invoking patch(1).
INCONVENIENCES
On System V machines, the generated patch file name will almost certainly exceed the 14 characters filename length limit.
SEE ALSO
shape_releas(1), vdiff(1), patch(1)
FILES
<name1>+2+<name2>.pat
21.8.119 SHAPE_PATCH(1)