[ilugd] Fwd: help

2004-10-29 Thread Sandip Bhattacharya


--  Forwarded Message  --

Subject: help
Date: Friday 29 Oct 2004 12:49 pm
From: N. K. Ray 
To: ilugd-dev-owner

I have 3 pentium 4 i wish to make pc cluster i have a hub and connecting
wires
the linux should be redhat linux 6.2 or higher .I willing to pay for the
expenses
Prof.N.K.Ray
Phone 27667855
mobile 9213109501
email nkray @ vsnl.com

---

-- 
Sandip Bhattacharya*Puroga Technologies   * [EMAIL PROTECTED]
Work: http://www.puroga.com* Home: http://www.sandipb.net

PGP/GPG Signature: 51A4 6C57 4BC6 8C82 6A65 AE78 B1A1 2280 A129 0FF3

We totally deny the allegations, and we're trying to identify the allegators.

___
ilugd mailinglist -- [EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/[EMAIL PROTECTED]/


Re: [ilugd] Fwd: help

2004-10-29 Thread Ritesh Agrawal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
Which type of cluster you want to deploy , There are mainly three type
of clusters.
1. High availablity
2. Loadbalancing
3.High performace computing
It is highly depend on your requirement.
Regards
Ritesh
C.No: 011 33110530
Sandip Bhattacharya wrote:
|
| --  Forwarded Message  --
|
| Subject: help
| Date: Friday 29 Oct 2004 12:49 pm
| From: N. K. Ray
| To: ilugd-dev-owner
|
| I have 3 pentium 4 i wish to make pc cluster i have a hub and connecting
| wires
| the linux should be redhat linux 6.2 or higher .I willing to pay for the
| expenses
| Prof.N.K.Ray
| Phone 27667855
| mobile 9213109501
| email nkray @ vsnl.com
|
| ---
|
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBgicZFoz+P95jnTIRAhfeAKCxet0uGB37W+0scntGslPuyImg+gCeM7MD
Hkw1jqSr+Iyw8gkJNpCnX7M=
=Qu9e
-END PGP SIGNATURE-
___
ilugd mailinglist -- [EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/[EMAIL PROTECTED]/


[ilugd] GFS Panic

2004-10-29 Thread Ritesh Agrawal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All,
I have a problem related to GFS deployment on a SAN volume,
SCENARIO:
Clustered Mail Server application
Environment:
RedHat ES 3.0
Redhat Cluster Suite
Cluster file system - GFS (ver 6.0) on ex3fs
DELL PowerEdge 1550 / 2650 / 1650 / 1750
EMC CX series
HBA Qlogix 23xx
SET-UP
DNS-- load balancer(s) -- cluster node + file lock management -- SAN
(mutli LUN)
single file lock manager in the cluster (one among the cluster nodes)
3 nodes in backend cluster to handle POP3 and SMTP requests
data stored in SAN, block size 128K, read / write cache enabled
all the nodes have direct access to SAN through fibre channel
In the migration process , when there were 3 nodes , all the systems
were running smoothly
but !
when I added some more load (mailboxes) with 2 more backend nodes, after
some time 2-3 nodes (any of the nodes in cluster) hanged with the
following error:
Oct 24 11:04:29 c5 kernel: GFS: Assertion failed on line 599 of file
inode.c
Oct 24 11:04:29 c5 kernel: GFS: assertion: (tmp_gh-gh_flags
GL_LOCAL_EXCL) || !(gh-gh_flags  GL_LOCAL_EXCL)
Oct 24 11:04:29 c5 kernel: GFS: time = 1095145469 Oct 24 11:04:29 c5
kernel: GFS: fsid=310farm:gfs01.2: glock = (4, 0)
Oct 24 11:04:29 c5 kernel:
Oct 24 11:04:29 c5 kernel: Kernel panic: GFS: Record message above and
reboot.
(LOCK MANAGER STILL KEEPS RUNNING and other nodes function properly)
I tried with different configurations of Lock manager but failed to get
it right.
Is the problem with
GFS (any limitations ?)
I/O
block size
lock management
or (my architecture itself)
How can i resolve this issue?
I am unable to find out proper reason of this.
Can someone of you who's had hands on this help me out?
Thanks for all those wonderful (non-witty) answers !
Thorough solutions on the above win a linux friend  :-)!
- --
Regards
Ritesh Agrawal
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBgke4Foz+P95jnTIRAoDgAKCwJ3aC61Pgs2hAS3yBpGQRQO5+4wCdHw9m
IK20cnSyJoQoKdD9OvaEKMM=
=nTE2
-END PGP SIGNATURE-
___
ilugd mailinglist -- [EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/[EMAIL PROTECTED]/


[ilugd] (no subject)

2004-10-29 Thread Narender Hooda


___
ilugd mailinglist -- [EMAIL PROTECTED]
http://frodo.hserus.net/mailman/listinfo/ilugd
Archives at: http://news.gmane.org/gmane.user-groups.linux.delhi 
http://www.mail-archive.com/[EMAIL PROTECTED]/


[ilugd] (fwd) [SECURITY] [DSA 577-1] New postgresql packages fix symlink vulnerability

2004-10-29 Thread Raj Mathur
[Please upgrade if you have PostgreSQL installed on any platform -- Raju]

This is an RFC 1153 digest.
(1 message)
--

Message-Id: [EMAIL PROTECTED]
From: [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Full-Disclosure] [SECURITY] [DSA 577-1] New postgresql packages fix symlink 
vulnerability
Date: Fri, 29 Oct 2004 12:20:33 +0200 (CEST)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

- --
Debian Security Advisory DSA 577-1 [EMAIL PROTECTED]
http://www.debian.org/security/ Martin Schulze
October 29th, 2004  http://www.debian.org/security/faq
- --

Package: postgresql
Vulnerability  : local
Problem-Type   : insecure temporary file
Debian-specific: no
CVE ID : CAN-2004-0977
Debian Bug : 278336

Trustix Security Engineers identified insecure temporary file creation
in a script included in the postgresql suite, an object-relational SQL
database.  This could lead an attacker to trick a user to overwrite
arbitrary files he has write access to.

For the stable distribution (woody) this problem has been fixed in
version 7.2.1-2woody6.

For the unstable distribution (sid) this problem has been fixed in
version 7.4.6-1.

We recommend that you upgrade your postgresql packages.


Upgrade Instructions
- 

wget url
will fetch the file for you
dpkg -i file.deb
will install the referenced file.

If you are using the apt-get package manager, use the line for
sources.list as given below:

apt-get update
will update the internal database
apt-get upgrade
will install corrected packages

You may use an automated update by adding the resources from the
footer to the proper configuration.


Debian GNU/Linux 3.0 alias woody
- 

  Source archives:


http://security.debian.org/pool/updates/main/p/postgresql/postgresql_7.2.1-2woody6.dsc
  Size/MD5 checksum:  966 ded5f8b8dc34a7e1916526cc4fd7dc5a

http://security.debian.org/pool/updates/main/p/postgresql/postgresql_7.2.1-2woody6.diff.gz
  Size/MD5 checksum:   119740 deb2918afe376395a218ebb3af0a58f2

http://security.debian.org/pool/updates/main/p/postgresql/postgresql_7.2.1.orig.tar.gz
  Size/MD5 checksum:  9237680 d075e9c49135899645dff57bc58d6233

  Architecture independent components:


http://security.debian.org/pool/updates/main/p/postgresql/postgresql-doc_7.2.1-2woody6_all.deb
  Size/MD5 checksum:  2069286 761ab47664aa2091451117b36c1ed27a

  Alpha architecture:


http://security.debian.org/pool/updates/main/p/postgresql/libecpg3_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:34456 ca83cb3c6c50453ef1b9d985f381f94b

http://security.debian.org/pool/updates/main/p/postgresql/libpgperl_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:68434 a74ea2a89fd9204c15b5f69bc72b2c20

http://security.debian.org/pool/updates/main/p/postgresql/libpgsql2_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:77692 3734b0f8deaa70a1d6767a3c64540ffd

http://security.debian.org/pool/updates/main/p/postgresql/libpgtcl_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:67398 df0adaaa2e9515a022535630e9578b5b

http://security.debian.org/pool/updates/main/p/postgresql/odbc-postgresql_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:   290006 a34a7323c402b398ab69632f5ba1502c

http://security.debian.org/pool/updates/main/p/postgresql/pgaccess_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:   425130 cff2adecf3350847358fcc73f342d7cb

http://security.debian.org/pool/updates/main/p/postgresql/postgresql_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:  1816990 e44d03b061447dd5c7f3a2398755d2d9

http://security.debian.org/pool/updates/main/p/postgresql/postgresql-client_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:   319618 60341c5a6e04bb7eb35d51e0b74438b8

http://security.debian.org/pool/updates/main/p/postgresql/postgresql-contrib_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:   387260 fca85d766f1b8a5b5bc36c65b7fd3ab0

http://security.debian.org/pool/updates/main/p/postgresql/postgresql-dev_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:   540920 17ec27505d8780845b5ee8c46b508447

http://security.debian.org/pool/updates/main/p/postgresql/python-pygresql_7.2.1-2woody6_alpha.deb
  Size/MD5 checksum:65062 71df8dfcc3bd1e01c61afef8d4f542a2

  ARM architecture:


http://security.debian.org/pool/updates/main/p/postgresql/libecpg3_7.2.1-2woody6_arm.deb
  Size/MD5 checksum:31544 dceca235c5f3761563c0496bbdf8081a

http://security.debian.org/pool/updates/main/p/postgresql/libpgperl_7.2.1-2woody6_arm.deb
  Size/MD5 checksum:64554 4685e3c5d18e05ee04aa9151f300f872