Discuss November 2006

discuss@lists.centos.org

253 participants
263 discussions

GPL java
by Jim Perrin 16 Nov '06

16 Nov '06

For the people who are currently interested in java as it relates to centos now that Sun has GPL'd java there are some things to be aware of. The folks at jpackage.org are pretty much all over this development but it's not the bright shiny news everyone has made it out to be. Sun did a very good thing by moving java under the GPL, and they should be commended for FINALLY seeing the light after the failure of the DLJ license BUT: 1. Sun did not open all of java under the GPL. There are still several chunks of java which remain license encumbered and will require community workarounds or further moves by Sun to open code. Currently these include the color management code, font rasteriser code, graphics rasteriser code, and several more. 2. Sun is not opening up the Java trademark, so any GPL'd distribution of java will not be called 'java', but something else. I've heard that iceweasel is taken, so I don't know what the next best option is. The fine folks at jpackage are working the details further. This basically means that for the time being, there will not be a gpl'd jdk in centos4, and packages will have to be distributed under the DLJ license (which I am not a fan of) or obtained from java.sun.com and used in conjunction with the jpackage sun-java-compat packages for best performance. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell

2 1

tar vs. star vs. something-else-I-don-t-know-about
by Alexey Loukianov 16 Nov '06

16 Nov '06

Hello all, today I've been sitting at work and upgrading a very-very-very old server with RedHat Linux 6.2 installed up to CentOS 3.8. The process went smoothly, as it is not the first time I was doing the things like this. Just after upgrading I went to rpm -qai list and got an interesting observation: there are at least two "tar" utilities installed on the system. One is tar, and second is star. [root@devel mrtg]# rpm -qi star Name : star Relocations: (not relocatable) Version : 1.5a08 Vendor: CentOS Release : 4 Build Date: Вск 29 Фев 2004 04:54:14 Install Date: Пнд 13 Ноя 2006 09:38:38 Build Host: centos3.wellhouse Group : Applications/Archiving Source RPM: star-1.5a08-4.src.rpm Size : 336744 License: GPL Signature : DSA/SHA1, Втр 16 Мар 2004 01:48:38, Key ID 7049e44d025e513b URL : http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private… Summary : An archiving tool with ACL support Description : Star saves many files together into a single tape or disk archive, and can restore individual files from the archive. Star supports ACL. [root@devel mrtg]# rpm -qi tar Name : tar Relocations: (not relocatable) Version : 1.14 Vendor: CentOS Release : 4 Build Date: Пнд 21 Фев 2005 18:58:37 Install Date: Срд 05 Апр 2006 19:48:51 Build Host: bhrama.build.karan.org Group : Applications/Archiving Source RPM: tar-1.14-4.src.rpm Size : 824393 License: GPL Signature : DSA/SHA1, Вск 27 Фев 2005 00:39:26, Key ID a53d0bab443e1821 Packager : Karanbir Singh <kbsingh(a)centos.org> URL : http://www.gnu.org/software/tar/ Summary : A GNU file archiving program. Description : The GNU tar program saves many files together in one archive and can restore individual files (or all of the files) from that archive. Tar can also be used to add supplemental files to an archive and to update or list files in the archive. Tar includes multivolume support, automatic archive compression/decompression, the ability to perform remote archives, and the ability to perform incremental and full backups. If you want to use tar for remote backups, you also need to install the rmt package. I would like to know, what are the differences between them? Which one should I use in the future? Is star compatible with amanda backup suite (I use amanda as a main backup software solution for our production environment servers)? Also, there may be other tar-like/compatible utilities shipped with CentOS3/4 that I simply don't know about. It would be great, if somebody will provide me with info (or a link to a place) about such utilities, and with a comparison between them all. Thanks in advance. -- С уважением, Alexey mailto:aloukianov@lavtech.ru

4 3

opens source trouble ticket
by Indunil Jayasooriya 16 Nov '06

16 Nov '06

Hi all, I am lookng for a truble ticket to install on my Cents os 4.4 server. RPM is always prefferd. Souce is also welcome. Have you done somethink like this before? What are the packages that you recomend for me. -- Thank you Indunil Jayasooriya

7 8

Why is your prefer mode for admin Centos ?
by Antonio Garcia 16 Nov '06

16 Nov '06

Webmin ? ssh ? console ? system-* ? Morote Traducciones SL Departamento de Informática

1 0

About download ISO image, again
by Stephen Liu 16 Nov '06

16 Nov '06

Hi folks, It comes to my notice that there is an server version - CentOS-4.4.ServerCD-x86_64.iso http://mirror.myriadnetwork.com/centos/4.4/isos/x86_64/ I'm going to run CentOS as server. What packages are included there? Is X packages included as well which should not be on a server creating a risk hole. However on another hand it will be convenient for me at the early stage of installation to search documents on Internet. Just retain X not started at boot and remove all their packages after installation finished. I don't expect connecting a workstation to the server to do this job at the beginning. Advice would be appreciated. TIA B.R. Stephen

6 9

hard drive failing in linux raid
by Joseph Cheng 15 Nov '06

15 Nov '06

Hello all. I have a server with a linux software raid1 setup between two drives of the same model....one hard drive as primary ide master and second hard drive as secondary master. Now primary master hard drive is displaying a lot of SMART errors so I would like to remove it and replace with another drive....different brand but same size. Partitions are /dev/md0 till /dev/md5. I think I know what to do based on mdadm man page and this list's archives but there is no harm in confirming right? ;) From this post http://lists.centos.org/pipermail/centos/2006-April/063076.html I plan on removing the old partitions from the array like this..... mdadm /dev/mdx -r /dev/hdax. Then I will shut down the server, replace the hard drive, make the server boot from second IDE drive and hopefully boot into Centos. From there do I have to manually create each /dev/mdx partition and then re-add them like this....mdadm /dev/mdx -a /dev/hdax ? That is what I am not sure about whether I have to partiton the drive exactly like the old one or if Centos mdadm can do some magic for me with a blank drive. TIA!!

5 6

CentOS-announce Digest, Vol 21, Issue 9
by centos-announce-request＠centos.org 15 Nov '06

15 Nov '06

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2006:0738 Low CentOS 3 i386 openssh - security update (Tru Huynh) 2. CESA-2006:0738 Low CentOS 3 x86_64 openssh - security update (Tru Huynh) 3. CESA-2006:0738 Low CentOS 3 ia64 openssh - security update (Pasi Pirhonen) 4. CESA-2006:0719 Moderate CentOS 4 ia64 nss_ldap - security update (Pasi Pirhonen) 5. CESA-2006:0738 Low CentOS 4 ia64 openssh - security update (Pasi Pirhonen) 6. CESA-2006:0738 Low CentOS 3 s390(x) openssh - security update (Pasi Pirhonen) 7. CESA-2006:0719 Moderate CentOS 4 s390(x) nss_ldap - security update (Pasi Pirhonen) 8. CESA-2006:0738 Low CentOS 4 s390(x) openssh - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Wed, 15 Nov 2006 16:30:18 +0100 From: Tru Huynh <tru(a)centos.org> Subject: [CentOS-announce] CESA-2006:0738 Low CentOS 3 i386 openssh - security update To: centos-announce(a)centos.org Message-ID: <20061115153018.GA28821(a)sillage.bis.pasteur.fr> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory CESA-2006:0738 openssh security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2006-0738.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/openssh-3.6.1p2-33.30.13.i386.rpm updates/i386/RPMS/openssh-askpass-3.6.1p2-33.30.13.i386.rpm updates/i386/RPMS/openssh-askpass-gnome-3.6.1p2-33.30.13.i386.rpm updates/i386/RPMS/openssh-clients-3.6.1p2-33.30.13.i386.rpm updates/i386/RPMS/openssh-server-3.6.1p2-33.30.13.i386.rpm source: updates/SRPMS/openssh-3.6.1p2-33.30.13.src.rpm You may update your CentOS-3 i386 installations by running the command: yum update openssh\* Tru -- Tru Huynh (CentOS-3 i386/x86_64 Package Maintenance) http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B

1 0

sshd logging with GMT times?
by David Mackintosh 15 Nov '06

15 Nov '06

Hi folks, while chasing down a logging-related situation, I happened to notice that when I connect via ssh to my system it makes the following logs: Nov 15 14:15:39 saturn sshd[29868]: Accepted password for dave from ::ffff:10.0.10.14 port 2833 ssh2 Nov 15 09:15:39 saturn sshd[29867]: Accepted password for dave from ::ffff:10.0.10.14 port 2833 ssh2 Nov 15 09:15:39 saturn sshd(pam_unix)[29869]: session opened for user dave by (uid=0) That is, sshd appears to log the connection with GMT (or UCT) before the child sshd logs it with local time. This is messing up one of my reporting processes, since I have syslog-ng configured to produce a new file for every day, and at the end of the day I try to scan the newest file for the day's events. So if I ssh to the system after 7PM local time, the "newest" file is the one from "tomorrow" which has the GMT timestamped entries, not the entries from today. How do I either tell sshd to always use local time, or tell it not to make the first entry? -- /\oo/\ / /()\ \ David Mackintosh | Public Key: dave(a)xdroop.com | http://www.xdroop.com/dave/gpg.html $ gpg --recv-keys --keyserver subkeys.pgp.net 4C032504 Mystery attachment? http://wiki.xdroop.com/space/GPG

4 3

System crashed & LVM1
by Guy Boisvert 15 Nov '06

15 Nov '06

Hi all! I'm new to this list. I wanted to have an opinion of the situation i'm facing now (i'm no expert in LVM). Last week, i had to re-install a system which had a system hard drive crash (it was clunking before it definitely died!). It was running on SuSE 9.0 before. I just finished to install a fresh copy of CentOS 4.4 on a new hard disk. I want to know if it's possible to "import" the old LVM array into the fresh CentOS install. We have 1 volume group (LVM1) that contains 3 whole hard drives. I had the time to save some informations before the system hard drive crashed definitely: I have vgcfgrestore info, i have volgroups_001.conf, i have the full /etc directory and pvdata. Here is a part of the info i have: PVDATA: ======= --- Physical volume --- PV Name /dev/sda VG Name volgroup_001 PV Size 298.09 GB [625142448 secs] / NOT usable 32.19 MB [LVM: 165 KB] PV# 1 PV Status available Allocatable yes (but full) Cur LV 1 PE Size (KByte) 32768 Total PE 9537 Free PE 0 Allocated PE 9537 PV UUID 5nc71v-D2mv-RpBX-3c3f-17tI-9ChT-mYctTg --- Volume group --- VG Name VG Access read/write VG Status NOT available/resizable VG # 0 MAX LV 256 Cur LV 1 Open LV 0 MAX LV Size 2 TB Max PV 256 Cur PV 3 Act PV 3 VG Size 670.53 GB PE Size 32 MB Total PE 21457 Alloc PE / Size 21457 / 670.53 GB Free PE / Size 0 / 0 VG UUID hf074V-P9DA-AmCU-F2pr-nfdD-QTaA-Ic0lH5 --- List of logical volumes --- pvdata -- logical volume "/dev/volgroup_001/loggroup_001" at offset 0 pvdata -- logical volume struct at offset 1 is empty pvdata -- logical volume struct at offset 2 is empty .... pvdata -- logical volume struct at offset 254 is empty pvdata -- logical volume struct at offset 255 is empty --- List of physical extents --- PE: 00000 LV: 001 LE: 00000 PE: 00001 LV: 001 LE: 00001 .... PE: 09535 LV: 001 LE: 09535 PE: 09536 LV: 001 LE: 09536 --- List of physical volume UUIDs --- 001: 5nc71v-D2mv-RpBX-3c3f-17tI-9ChT-mYctTg 002: 8bsBQR-bTiI-Zky5-Qvpu-oMtp-x62p-0uWwha 003: 6xAILO-KhgO-0U0c-Ir88-xZ8y-AIlc-JtPjDg --- NEW Physical volume --- PV Name /dev/hdc VG Name volgroup_001 PV Size 30.21 MB [61872 secs] PV# 2 PV Status NOT available Allocatable NO Cur LV 0 PE Size (KByte) 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID 8bsBQR-bTiI-Zky5-Qvpu-oMtp-x62p-0uWwha --- Volume group --- VG Name VG Access read/write VG Status NOT available/resizable VG # 0 MAX LV 256 Cur LV 1 Open LV 0 MAX LV Size 2 TB Max PV 256 Cur PV 3 Act PV 3 VG Size 670.53 GB PE Size 32 MB Total PE 21457 Alloc PE / Size 21457 / 670.53 GB Free PE / Size 0 / 0 VG UUID hf074V-P9DA-AmCU-F2pr-nfdD-QTaA-Ic0lH5 --- List of logical volumes --- pvdata -- logical volume "/dev/volgroup_001/loggroup_001" at offset 0 pvdata -- logical volume struct at offset 1 is empty .... pvdata -- logical volume struct at offset 254 is empty pvdata -- logical volume struct at offset 255 is empty --- List of physical extents --- --- List of physical volume UUIDs --- 001: 5nc71v-D2mv-RpBX-3c3f-17tI-9ChT-mYctTg 002: 8bsBQR-bTiI-Zky5-Qvpu-oMtp-x62p-0uWwha 003: 6xAILO-KhgO-0U0c-Ir88-xZ8y-AIlc-JtPjDg --- Physical volume --- PV Name /dev/hdd VG Name volgroup_001 PV Size 186.31 GB [390721968 secs] / NOT usable 32.19 MB [LVM: 151 KB] PV# 3 PV Status NOT available Allocatable yes (but full) Cur LV 1 PE Size (KByte) 32768 Total PE 5960 Free PE 0 Allocated PE 5960 PV UUID 6xAILO-KhgO-0U0c-Ir88-xZ8y-AIlc-JtPjDg --- Volume group --- VG Name VG Access read/write VG Status NOT available/resizable VG # 0 MAX LV 256 Cur LV 1 Open LV 0 MAX LV Size 2 TB Max PV 256 Cur PV 3 Act PV 3 VG Size 670.53 GB PE Size 32 MB Total PE 21457 Alloc PE / Size 21457 / 670.53 GB Free PE / Size 0 / 0 VG UUID hf074V-P9DA-AmCU-F2pr-nfdD-QTaA-Ic0lH5 --- List of logical volumes --- pvdata -- logical volume "/dev/volgroup_001/loggroup_001" at offset 0 pvdata -- logical volume struct at offset 1 is empty pvdata -- logical volume struct at offset 2 is empty .... pvdata -- logical volume struct at offset 254 is empty pvdata -- logical volume struct at offset 255 is empty --- List of physical extents --- PE: 00000 LV: 001 LE: 15497 PE: 00001 LV: 001 LE: 15498 .... PE: 05958 LV: 001 LE: 21455 PE: 05959 LV: 001 LE: 21456 --- List of physical volume UUIDs --- 001: 5nc71v-D2mv-RpBX-3c3f-17tI-9ChT-mYctTg 002: 8bsBQR-bTiI-Zky5-Qvpu-oMtp-x62p-0uWwha 003: 6xAILO-KhgO-0U0c-Ir88-xZ8y-AIlc-JtPjDg lvmdiskscan -- reading all disks / partitions (this may take a while...) lvmdiskscan -- /dev/sda [ 298.09 GB] USED LVM whole disk lvmdiskscan -- /dev/hdc [ 186.31 GB] USED LVM whole disk lvmdiskscan -- /dev/hdd [ 186.31 GB] USED LVM whole disk lvmdiskscan -- /dev/hda1 [ 1004.03 MB] Primary LINUX swap partition [0x82] lvmdiskscan -- /dev/hda2 [ 27.59 GB] Primary LINUX native partition [0x83] lvmdiskscan -- /dev/hda3 [ 45.95 GB] Primary LINUX native partition [0x83] lvmdiskscan -- 4 disks lvmdiskscan -- 3 whole disks lvmdiskscan -- 0 loop devices lvmdiskscan -- 0 multiple devices lvmdiskscan -- 0 network block devices lvmdiskscan -- 3 partitions lvmdiskscan -- 0 LVM physical volume partitions VGCFGRESTORE ============ vgcfgrestore -- INFO: using backup file "/etc/lvmconf/volgroup_001.conf" --- Volume group --- VG Name volgroup_001 VG Access read/write VG Status NOT available/resizable VG # 0 MAX LV 256 Cur LV 1 Open LV 0 MAX LV Size 2 TB Max PV 256 Cur PV 3 Act PV 3 VG Size 670.53 GB PE Size 32 MB Total PE 21457 Alloc PE / Size 21457 / 670.53 GB Free PE / Size 0 / 0 VG UUID hf074V-P9DA-AmCU-F2pr-nfdD-QTaA-Ic0lH5 --- Logical volume --- LV Name /dev/volgroup_001/loggroup_001 VG Name volgroup_001 LV Write Access read/write LV Status NOT available LV # 1 # open 0 LV Size 670.53 GB Current LE 21457 Allocated LE 21457 Allocation next free Read ahead sectors 1024 Block device 58:0 --- Physical volume --- PV Name /dev/sda VG Name volgroup_001 PV Size 298.09 GB [625142448 secs] / NOT usable 32.19 MB [LVM: 165 KB] PV# 1 PV Status available Allocatable yes (but full) Cur LV 1 PE Size (KByte) 32768 Total PE 9537 Free PE 0 Allocated PE 9537 PV UUID 5nc71v-D2mv-RpBX-3c3f-17tI-9ChT-mYctTg --- Physical volume --- PV Name /dev/hdc VG Name volgroup_001 PV Size 186.31 GB [390721968 secs] / NOT usable 32.19 MB [LVM: 151 KB] PV# 2 PV Status NOT available Allocatable yes (but full) Cur LV 1 PE Size (KByte) 32768 Total PE 5960 Free PE 0 Allocated PE 5960 PV UUID 8bsBQR-bTiI-Zky5-Qvpu-oMtp-x62p-0uWwha --- Physical volume --- PV Name /dev/hdd VG Name volgroup_001 PV Size 186.31 GB [390721968 secs] / NOT usable 32.19 MB [LVM: 151 KB] PV# 3 PV Status NOT available Allocatable yes (but full) Cur LV 1 PE Size (KByte) 32768 Total PE 5960 Free PE 0 Allocated PE 5960 PV UUID 6xAILO-KhgO-0U0c-Ir88-xZ8y-AIlc-JtPjDg Thanks if advance and long live to CentOS! Guy Boisvert

1 0

stange lockd issue on CentOS 4.4
by Alexey Loukianov 15 Nov '06

15 Nov '06

Greetings, CentOS. After up2dating one of the corporate mail servers to CentOS 4.4 (was CentOS 4.2) and upgrading kernel to kernel-smp-2.6.9-42.0.3.EL, the following kernel messages started to appear in syslog: [root@gamma ~]# dmesg ........... ...CUT..... ........... lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 lockd: unexpected unlock status: 1 Rebooted with an older kernel (2.6.9-34.0.2.ELsmp), but the problem persists. This server utilizes NFS share as a storage volume for user mail boxes, the NFS server is also a CentOS 4.4 server, also with the kernel, up2dated to kernel-smp-2.6.9-42.0.3.EL few weeks ago. As this is a production environment, I can't simply go and reboot NFS server to an older kernel - this would lead to a small amount of downtime, which is undesirable for me. Could someone help me to understand what does that messages mean, why did they appear, and what caveats they may cause to me except for spammed syslog? Thanks in advance. -- Best regards, Alexey Loukianov mailto:aloukianov@lavtech.ru Software Development Department, Lavtech Corp http://mnogo.ru, http://lavtech.ru

1 0

← Newer
1
...
11
12
13
14
15
16
17
...
27
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2006