09-04-2002
It should run just fine on a 2-4 CPU box.
According to the HOW-TO (you should really learn how to use google...), the 2.2 series kernels should theoretically work for up to 16 CPUs on an Intel machine. Redhat 7.3 uses a kernel in the 2.4 tree, so I can't be 100% sure of any changes.
Here is the HOW-TO I am referring to:
http://www.tldp.org/HOWTO/SMP-HOWTO.html
7 More Discussions You Might Find Interesting
1. SCO
I have a dell machine Dell 2600 PowerEdge it has two processor (intel Xeon ).
Is there a path or a software that will work with SCO unix in order to enable second processor and how would i know that the second processor is active.
Thanks a lot guys . (1 Reply)
Discussion started by: josramon
1 Replies
2. UNIX for Dummies Questions & Answers
If the strength of Unix based operating systems such as Linux and Red Hat are based on the fact that they are open-source. Who will provide support for personal computers or average users that uses these operating systems. Wouldn't the absence of some structured and formal support system inhibit... (8 Replies)
Discussion started by: wmosley2
8 Replies
3. Linux Benchmarks
System:
CPU/Speed: Dual Intel Xeon 2.4Ghz
Ram: 2 GB DDR 266 SDRAM
Motherboard: SuperMicro X5DE8-GG
Bus: 533MHz/400MHz system bus -
Cache: 512KB
HD Controller: EIDE Serverworks™ GC-SL Chipset
Extra GCC compiler flags:
-s... (3 Replies)
Discussion started by: Neo
3 Replies
4. Red Hat
I have installed redhat linux 9.0 on P4 HT machine. The grub boot loader shows path to smp mode and normal mode. when machine shut downs from smp version kernal , need to press the power button to power off. But in normal mode the system shut downs or power downs automatically(ie, full... (2 Replies)
Discussion started by: pcsaji
2 Replies
5. Programming
Interesting issue. There was some discussion on the LKML last year regarding the potential problems in concurrent applications reusing file descriptors in various scenarios. The main issue is that the reuse of a file descriptor and reception of data in a threaded application can be confused pretty... (1 Reply)
Discussion started by: ramen_noodle
1 Replies
6. High Performance Computing
Hola, he instalado mpich2 vs. 1.2.1p1 en un cluster de biprocesadores con las opciones por defecto (antes usaba ssm pero visto que se quedaba colgado, lo he dejado con nemesis).
El caso es que quisiera que cada vez que lanzo un job (por ejemplo de 2 procesos), cada proceso del trabajo se fuera... (1 Reply)
Discussion started by: Sonia_
1 Replies
7. Programming
The SCO OSR 5.7 system was migrated from older HP DL360 to new DL380 G7. The SMP feature was not activated on older box, it is activated now on this 4 core Xeon.
A s/w we maintain has been copied without any change over to the new box. I noticed that the application profiling does not show any... (4 Replies)
Discussion started by: migurus
4 Replies
LEARN ABOUT DEBIAN
svnpath
SVNPATH(1) SVNPATH(1)
NAME
svnpath - output svn url with support for tags and branches
SYNOPSIS
svnpath
svnpath tags
svnpath branches
svnpath trunk
DESCRIPTION
svnpath is intended to be run in a Subversion working copy.
In its simplest usage, svnpath with no parameters outputs the svn url for the repository associated with the working copy.
If a parameter is given, svnpath attempts to instead output the url that would be used for the tags, branches, or trunk. This will only
work if it's run in the top-level directory that is subject to tagging or branching.
For example, if you want to tag what's checked into Subversion as version 1.0, you could use a command like this:
svn cp $(svnpath) $(svnpath tags)/1.0
That's much easier than using svn info to look up the repository url and manually modifying it to derive the url to use for the tag, and
typing in something like this:
svn cp svn+ssh://my.server.example/svn/project/trunk svn+ssh://my.server.example/svn/project/tags/1.0
svnpath uses a simple heuristic to convert between the trunk, tags, and branches paths. It replaces the first occurrence of trunk, tags, or
branches with the name of what you're looking for. This will work ok for most typical Subversion repository layouts.
If you have an atypical layout and it does not work, you can add a ~/.svnpath file. This file is perl code, which can modify the path in
$url. For example, the author uses this file:
#!/usr/bin/perl
# svnpath personal override file
# For d-i I sometimes work from a full d-i tree branch. Remove that from
# the path to get regular tags or branches directories.
$url=~s!d-i/(rc|beta)[0-9]+/!!;
$url=~s!d-i/sarge/!!;
1
LICENSE
GPL version 2 or later
AUTHOR
Joey Hess <joey@kitenet.net>
Debian Utilities 2013-12-23 SVNPATH(1)