Re: [CentOS] Jumbo Frame performance or lackof?
On 6/26/11, Gordon Messmer wrote: > On 06/25/2011 01:13 PM, Emmanuel Noobadmin wrote: >> The results were unexpected. The higher the MTU on the sending NIC, >> the lower the file transfer speed. > > What kind of switch are you using? If your switches don't support large > packets, you'll also see slowdowns like that. It's a 3Com 2920 now known as HP V1910 switch. Jumbo frames up to 10K is supposed to be supported. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Jumbo frames problem with Realtek NICs?
On 6/26/11, Ross Walker wrote: > Jumbo frames don't give higher throughput, but lower CPU. > > I find standard frames give better throughput for 4K block sizes like one > typically finds with file systems. > > You really don't need to go to jumbo frames until you reach 10Gbps speed. This was pretty much my conclusion (only useful at higher speeds and for reducing packet processing overheads) after further reading since the experiment. Now the question is whether the overheads reduction, even at sub-10GBs speeds, may be significant if the host/guest are VMs instead of actual physical machines. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Jumbo frames problem with Realtek NICs?
On 6/26/11, Gordon Messmer wrote: > On 06/25/2011 12:05 PM, Emmanuel Noobadmin wrote: >> >> Default Driver -> ElRepo driver >> 1500 MTU -> 3000 MTU = OK > > That's not going to be reliable. Sooner or later, you'll see the mount > hang (any transfer may) if your MTUs don't match. Thanks for the warning although I wasn't on planning on using mismatched MTU for real operations :) It was for the purpose of determining the effects of using the different MTU that I was doing that. Even if there wasn't the risk of a hang, for the sake of better performance, it seems that matched MTU are better anyway. The sys time component increased on the receiving side in relation to the receiver's MTU but drops significantly (8~10%) when non-default MTU are matched. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Strange issue's with LDAP and too many open files
Check also 'timeout' at slapd.conf. I solved my problem setting "timeout 30" at slapd.conf On Fri, Jun 24, 2011 at 10:49 AM, Sebastiaan Koetsier | proserve wrote: > Hi Steve, > > The change of /etc/sysconfig/ldap did the trick, thanks for your help! > > Cheers, > Sebastiaan. > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Jumbo frames problem with Realtek NICs?
On Jun 25, 2011, at 3:05 PM, Emmanuel Noobadmin wrote: > Ironically, even at 1500MTU, I was able to hit the full 100+ MB/s > speed available on a single Gigabit link so it seems my experiment was > a bit futile. Jumbo frames don't give higher throughput, but lower CPU. I find standard frames give better throughput for 4K block sizes like one typically finds with file systems. You really don't need to go to jumbo frames until you reach 10Gbps speed. -Ross ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] sendmail - smtp security/authentication & port 587 issues
On Sun, 26 Jun 2011, Alexander Dalloz wrote: > Am 25.06.2011 23:50, schrieb Max Pyziur: >> >> Greetings, >> >> I'm refining a CentOs configuration installation, now just over one month >> old running on a colocated production server. Previously, we ran a version >> of Fedora for over seven years. >> >> Specifically, I'm reviewing our sendmail configuration, both with respect >> to authentication and port usage. >> >> Previously, we had the following line in the sendmail.mc line: >> define(`confAUTH_MECHANISMS', `DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl > > Though defined, you seem not to have made use of it; no SMTP AUTH in > your description of the previous setup. > >> To authenticate, users would first have to POP their mail. >> >> A klunky script would scan appropriate log files and copy relevant IP >> addresses to the /etc/mail/access file that would be regenerated every >> 5 minutes via cron. >> >> Once the IP address was in the /etc/mail/access.db a user could be >> authenticated and be allowed to send email using the machine as smtp. > > That sounds as a poor version of POP-before-SMTP. Which mechanism > deletes the IP from the access_db? It is a POP-before-SMTP, poor or otherwise. The IPs in access_db are taken from the /var/log/maillog file. They effectively get "deleted" by way of the logrotate function (weekly and monthly). IPs in the /etc/mail/access.db are based on the current /var/log/maillog file. Once the /var/log/maillog file is rotated (4am Sunday), the added IPs disappear. > By no means SMTP AUTH was used, just plain relay permission based on the > access_db. > >> Is there a better way of doing this? > > Definitely. I'm open to suggestions. Currently, I'm running on a default CentOs-Sendmail configuration. >> Port 587 issues: >> Verizon DSL filters out requests on port 25 to smtp servers not belonging >> to verizon.net. An alternative is to use port 587 for smtp purposes. >> >> Are there any views in this CentOs user community on this? > > Yes, configure SMTP AUTH and offer the submission service to the users. > Everything is prepared and documented within the sendmail.mc CentOS > ships with. You just have to think about which backend SASL shall use to > verify auth credentials. > >> Much thanks. >> >> Max Pyziur >> p...@brama.com [recycle] > Alexander > > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Jumbo Frame performance or lackof?
On 06/25/2011 01:13 PM, Emmanuel Noobadmin wrote: > The results were unexpected. The higher the MTU on the sending NIC, > the lower the file transfer speed. What kind of switch are you using? If your switches don't support large packets, you'll also see slowdowns like that. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] sendmail - smtp security/authentication & port 587 issues
Am 25.06.2011 23:50, schrieb Max Pyziur: > > Greetings, > > I'm refining a CentOs configuration installation, now just over one month > old running on a colocated production server. Previously, we ran a version > of Fedora for over seven years. > > Specifically, I'm reviewing our sendmail configuration, both with respect > to authentication and port usage. > > Previously, we had the following line in the sendmail.mc line: > define(`confAUTH_MECHANISMS', `DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl Though defined, you seem not to have made use of it; no SMTP AUTH in your description of the previous setup. > To authenticate, users would first have to POP their mail. > > A klunky script would scan appropriate log files and copy relevant IP > addresses to the /etc/mail/access file that would be regenerated every > 5 minutes via cron. > > Once the IP address was in the /etc/mail/access.db a user could be > authenticated and be allowed to send email using the machine as smtp. That sounds as a poor version of POP-before-SMTP. Which mechanism deletes the IP from the access_db? By no means SMTP AUTH was used, just plain relay permission based on the access_db. > Is there a better way of doing this? Definitely. > Port 587 issues: > Verizon DSL filters out requests on port 25 to smtp servers not belonging > to verizon.net. An alternative is to use port 587 for smtp purposes. > > Are there any views in this CentOs user community on this? Yes, configure SMTP AUTH and offer the submission service to the users. Everything is prepared and documented within the sendmail.mc CentOS ships with. You just have to think about which backend SASL shall use to verify auth credentials. > Much thanks. > > Max Pyziur > p...@brama.com Alexander ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] sendmail - smtp security/authentication & port 587 issues
Am 25.06.2011 23:50, schrieb Max Pyziur: > > Greetings, > > I'm refining a CentOs configuration installation, now just over one month > old running on a colocated production server. Previously, we ran a version > of Fedora for over seven years. > > Specifically, I'm reviewing our sendmail configuration, both with respect > to authentication and port usage. > > Previously, we had the following line in the sendmail.mc line: > define(`confAUTH_MECHANISMS', `DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl Though defined, you seem not to have made use of it; no SMTP AUTH in your description of the previous setup. > To authenticate, users would first have to POP their mail. > > A klunky script would scan appropriate log files and copy relevant IP > addresses to the /etc/mail/access file that would be regenerated every > 5 minutes via cron. > > Once the IP address was in the /etc/mail/access.db a user could be > authenticated and be allowed to send email using the machine as smtp. That sounds as a poor version of POP-before-SMTP. Which mechanism deletes the IP from the access_db? By no means SMTP AUTH was used, just plain relay permission based on the access_db. > Is there a better way of doing this? Definitely. > Port 587 issues: > Verizon DSL filters out requests on port 25 to smtp servers not belonging > to verizon.net. An alternative is to use port 587 for smtp purposes. > > Are there any views in this CentOs user community on this? Yes, configure SMTP AUTH and offer the submission service to the users. Everything is prepared and documented within the sendmail.mc CentOS ships with. You just have to think about which backend SASL shall use to verify auth credentials. > Much thanks. > > Max Pyziur > p...@brama.com Alexander ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Jumbo frames problem with Realtek NICs?
On 06/25/2011 12:05 PM, Emmanuel Noobadmin wrote: > > Default Driver -> ElRepo driver > 1500 MTU -> 3000 MTU = OK That's not going to be reliable. Sooner or later, you'll see the mount hang (any transfer may) if your MTUs don't match. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] sendmail - smtp security/authentication & port 587 issues
Greetings, I'm refining a CentOs configuration installation, now just over one month old running on a colocated production server. Previously, we ran a version of Fedora for over seven years. Specifically, I'm reviewing our sendmail configuration, both with respect to authentication and port usage. Previously, we had the following line in the sendmail.mc line: define(`confAUTH_MECHANISMS', `DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl To authenticate, users would first have to POP their mail. A klunky script would scan appropriate log files and copy relevant IP addresses to the /etc/mail/access file that would be regenerated every 5 minutes via cron. Once the IP address was in the /etc/mail/access.db a user could be authenticated and be allowed to send email using the machine as smtp. Is there a better way of doing this? Port 587 issues: Verizon DSL filters out requests on port 25 to smtp servers not belonging to verizon.net. An alternative is to use port 587 for smtp purposes. Are there any views in this CentOs user community on this? Much thanks. Max Pyziur p...@brama.com ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Jumbo Frame performance or lackof?
Emmanuel Noobadmin wrote:
> I'm wondering, that since Jumbo Frames was supposed to be better for
> bulk transfers, why am I seeing these results? Is it the ElRepo
> drivers I used to enable higher MTUs or possibly some kind of oddity
> with the realtek NICs I am using? Or am I mistaken about the benefits
> of jumbo frames and that they are only beneficial in specific
> configurations, perhaps only with higher network speeds and enough
> packets at 1500 MTU to overwhelm packet handling hardware?
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>
I googled about Jumbo Frames ("jumbo frames impact") and 2 top hits are
very interesting:
http://sd.wareonearth.com/~phil/jumbo.html
http://www.chelsio.com/jumbo_enet_frames.html
I guess if you are not happy with speed provided by Realtek you should
definitely buy more expensive NIC's with support of 9000K packets.
Ljubomir
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Jumbo frames problem with Realtek NICs?
Emmanuel Noobadmin wrote: > Ironically, even at 1500MTU, I was able to hit the full 100+ MB/s > speed available on a single Gigabit link so it seems my experiment was > a bit futile. > ___ > CentOS mailing list > CentOS@centos.org > http://lists.centos.org/mailman/listinfo/centos > > I am glad the "honor" of the Realtek NIC's is defended in the sense that they are not cheap crap, just cheap :-) Ljubomir ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] Jumbo Frame performance or lackof?
After successfully getting higher MTU to work on my Realtek NICs, I started testing the impact of higher MTU on file transfers using NFS exported ramdisk to ramdisk. The results were unexpected. The higher the MTU on the sending NIC, the lower the file transfer speed. I tested by using time cp to copy a 1GB file (In case compression might affect the results, so I dd the test file from the CentOS DVD ISO) The average of 6 runs per MTU with varying MTU on the receiving NICs MTU 1500 = 116.34 MB/s MTU 3000 = 103.42 MB/s MTU 4000 = 102.52 MB/s I was actually planning to do 1500, 3000, 4500, 6000 and 7200. However, I was surprised to discover although I had two seemingly identical Realtek PCI-E nics, the sending NIC could only go up to 4K. I'm wondering, that since Jumbo Frames was supposed to be better for bulk transfers, why am I seeing these results? Is it the ElRepo drivers I used to enable higher MTUs or possibly some kind of oddity with the realtek NICs I am using? Or am I mistaken about the benefits of jumbo frames and that they are only beneficial in specific configurations, perhaps only with higher network speeds and enough packets at 1500 MTU to overwhelm packet handling hardware? ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Jumbo frames problem with Realtek NICs?
On 6/26/11, Gordon Messmer wrote: > I don't know anything specifically about those cards, but you'll see > that behavior on any card unless all of the hosts on a broadcast domain > are using the same MTU. You need to set all of the devices on a LAN > segment, including the router, to the same MTU. Thanks for this note, but it didn't seem to be necessary in my case. I just finished updating the drivers and running some test, the results were this. In all cases, default 1500 MTU to 1500MTU = OK for both default and Elrepo drivers. NFS Host -> NFS Client Default Drivers for both 1500 MTU -> 3000 MTU = fail 3000 MTU -> 3000 MTU = fail Default Driver -> ElRepo driver 1500 MTU -> 3000 MTU = OK 3000 MTU -> x MTU = fail ElRepo -> ElRepo driver Both OK So the MTU problem appears to be firmly pinpointed to the default RTL drivers and both receiving/transmitting NICs must be using the ElRepo drivers to work properly at higher MTU. Ironically, even at 1500MTU, I was able to hit the full 100+ MB/s speed available on a single Gigabit link so it seems my experiment was a bit futile. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Shared object packaging in rpm
>> http://www.ibm.com/developerworks/library/l-shobj/ Thanks, that was informative. >> As Ljubomir said, libasync_wmi_lib.so.0 will be a symlink to >> libasync_wmi_lib.so.0.0.1. You can use objdump to find the soname(s) for >> shared objects, e.g: >> >> objdump -p /path/to/libasync_wmi_lib.so.0.0.1 | grep SONAME >> >> or just run ldconfig against them and observe what symlinks are created. They are actually not symlinked, they are different sizes but objdump does suggest the SONAME is libasync_wmi_lib.so.0 for both? The odd part is ldd ran against the two binaries produced from the package (samba portion) only need glibc and popt libraries. The actual python stub that kicks off the make and install portions manually copies the binaries into a logical place, yet copies the so's into a lib/python directory under some user chosen prefix beside a pysamba module package in that directory. Looking through its code, it attempts to locate these libraries so unless I plan on leveraging some python I presume I can package away without any of this. >I forgot to say, wrt packaging, you should create the symlink(s) in the >buildroot so that they are packaged rather than just running ldconfig in >%post. That way, the symlinks are owned by the rpm package and won't be >left dangling when the package is uninstalled. That's another good point I'll keep in mind! All this has been informative, thanks a lot guys, jlc ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Jumbo frames problem with Realtek NICs?
On 06/23/2011 10:20 AM, Emmanuel Noobadmin wrote: > I assumed 4K would still be better than nothing but unfortunately > bumping up the MTU to anything else but 1.5K caused the file transfers > (using NFS for easy testing), to hang at random points or more > accurate slow to a crawl. I don't know anything specifically about those cards, but you'll see that behavior on any card unless all of the hosts on a broadcast domain are using the same MTU. You need to set all of the devices on a LAN segment, including the router, to the same MTU. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how do determine last file system on disk?
On Saturday, June 25, 2011 07:46:01 AM Rudi Ahlers wrote: > Does anyone know how to determine which file system a disk was formatted > with, if fdisk -l doesn't show it? blkid -s TYPE On a C5 box here: [root@backup670 ~]# blkid -s TYPE /dev/mapper/vg_backup670-lv_root: TYPE="ext3" /dev/md1: TYPE="swap" /dev/md0: TYPE="ext3" /dev/sdb2: TYPE="swap" /dev/sdb1: TYPE="ext3" /dev/sda2: TYPE="swap" /dev/sda1: TYPE="ext3" /dev/hda: TYPE="iso9660" /dev/vg_backup670/lv_root: TYPE="ext3" /dev/mapper/pachy--mirror-home: TYPE="xfs" /dev/vg_opt/lv_pachy: TYPE="ext4" /dev/pachy-mirror/home: TYPE="xfs" /dev/mapper/vg_opt-lv_pachy: TYPE="ext4" [root@backup670 ~]# On a RHEL 6.1 box here: [root@www ~]# blkid -s TYPE /dev/sdd1: TYPE="LVM2_member" /dev/sde1: TYPE="LVM2_member" /dev/sdk1: TYPE="LVM2_member" /dev/sdn1: TYPE="xfs" /dev/sdg1: TYPE="ext4" /dev/sds1: TYPE="LVM2_member" /dev/sdy1: TYPE="LVM2_member" /dev/sdaa1: TYPE="ext4" /dev/sdag1: TYPE="linux_raid_member" /dev/sdx1: TYPE="LVM2_member" /dev/sdaf1: TYPE="linux_raid_member" /dev/sdad1: TYPE="ext3" /dev/sdah1: TYPE="ext4" /dev/sdah2: TYPE="LVM2_member" /dev/mapper/vg_www-lv_root: TYPE="ext4" /dev/mapper/vg_www-lv_swap: TYPE="swap" /dev/md127: TYPE="ext3" /dev/mapper/vg_bak2-lv_lobak: TYPE="ext4" [root@www ~]# Useful stuff. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how do determine last file system on disk?
On Sat, 25 Jun 2011, Always Learning wrote: > To: CentOS mailing list > From: Always Learning > Subject: Re: [CentOS] how do determine last file system on disk? > > > >> Does anyone know how to determine which file system a disk was >> formatted with, if fdisk -l doesn't show it? > > I would use gparted from the command line or from Gnome's / > Applications / System Tools menu > > yum install gparted Yes I second that. I prefer to use the GUI version, as you can see at a glance all you need to know about a drive's partitions. Plus you can make a screenshot of a disk's partitions, in case you loose a disk and have to replace it, and re-partition it, like I had to earlier this year. Just follow whats on the screenshot. Kind Regards, Keith Roberts - Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] - ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how do determine last file system on disk?
On 06/25/2011 06:46 AM, Rudi Ahlers wrote:
> Hi all,
>
> Does anyone know how to determine which file system a disk was formatted with,
> if fdisk -l doesn't show it?
[snip]
> I need to see what data is on a bunch of disks that I found in storage and
> would
> prefer to first check if there's anything of use on them before I format them
Running "file -s /dev/{some_partition}" will generally tell you something.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how do determine last file system on disk?
At Sat, 25 Jun 2011 13:46:01 +0200 CentOS mailing list wrote: > > > > Hi all, > > Does anyone know how to determine which file system a disk was formatted > with, if fdisk -l doesn't show it? > > > > usb-storage: device found at 5 > usb-storage: waiting for device to settle before scanning > Vendor: Model: Rev: > Type: Direct-Access ANSI SCSI revision: 02 > sd 7:0:0:0: Attached scsi disk sda > sd 7:0:0:0: Attached scsi generic sg0 type 0 > usb-storage: device scan complete > usb 1-4: USB disconnect, address 5 > usb 1-4: new high speed USB device using ehci_hcd and address 6 > usb 1-4: configuration #1 chosen from 1 choice > scsi8 : SCSI emulation for USB Mass Storage devices > usb-storage: device found at 6 > usb-storage: waiting for device to settle before scanning > Vendor: Model: Rev: > Type: Direct-Access ANSI SCSI revision: 02 > sd 8:0:0:0: Attached scsi disk sda > sd 8:0:0:0: Attached scsi generic sg0 type 0 > usb-storage: device scan complete > [root@HP-DL360 ~]# fdisk -l /dev/sda > [root@HP-DL360 ~]# > > > > > I need to see what data is on a bunch of disks that I found in storage and > would prefer to first check if there's anything of use on them before I > format them If 'fdisk -l /dev/sda' does not show anything, either the disks were never partitioned or formatted, at least not as a bare drive. What kind of disk is this (I know it says USB above, but I am assuming these are bare disk(s) that you installed in a USB enclosure). It is *possible* these disks were part of a *hardware* RAID array, in which case only the hardware RAID would know how to deal with them (they would have some vendor-specific metadata / superblock on them somewhere). If the disks are not partitularly large (< 1TB) if they were actually in use they would likely have a MS-DOS partition table (which fdisk -l would be displaying). If they are larger disks they might have gpt partition table (parted would show this). It is possible that they have a Solaris disk label (if they were in a Solaris machine). It is *possible* that someone used them as part of a Linux software RAID array using the whole disk, in which case there might be a MD superblock on them (mdadm might see it) and it is ALSO possible that they were part of a LVM volume group, also using the whole disk as a PV, in which case there should be LVM metadata on them (lvm might see this). If none of the above, they are just 'factory fresh', never used disks. -- Robert Heller -- 978-544-6933 / hel...@deepsoft.com Deepwoods Software-- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] how do determine last file system on disk?
> Does anyone know how to determine which file system a disk was > formatted with, if fdisk -l doesn't show it? I would use gparted from the command line or from Gnome's / Applications / System Tools menu yum install gparted -- With best regards, Paul. England, EU. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
[CentOS] how do determine last file system on disk?
Hi all, Does anyone know how to determine which file system a disk was formatted with, if fdisk -l doesn't show it? usb-storage: device found at 5 usb-storage: waiting for device to settle before scanning Vendor: Model: Rev: Type: Direct-Access ANSI SCSI revision: 02 sd 7:0:0:0: Attached scsi disk sda sd 7:0:0:0: Attached scsi generic sg0 type 0 usb-storage: device scan complete usb 1-4: USB disconnect, address 5 usb 1-4: new high speed USB device using ehci_hcd and address 6 usb 1-4: configuration #1 chosen from 1 choice scsi8 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 6 usb-storage: waiting for device to settle before scanning Vendor: Model: Rev: Type: Direct-Access ANSI SCSI revision: 02 sd 8:0:0:0: Attached scsi disk sda sd 8:0:0:0: Attached scsi generic sg0 type 0 usb-storage: device scan complete [root@HP-DL360 ~]# fdisk -l /dev/sda [root@HP-DL360 ~]# I need to see what data is on a bunch of disks that I found in storage and would prefer to first check if there's anything of use on them before I format them -- Kind Regards Rudi Ahlers SoftDux Website: http://www.SoftDux.com Technical Blog: http://Blog.SoftDux.com Office: 087 805 9573 Cell: 082 554 7532 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Shared object packaging in rpm
On 25/06/11 10:04, Ned Slider wrote: > On 25/06/11 02:15, Joseph L. Casale wrote: >> I whipped up a quick spec to package Zenoss' wmi client and noticed it >> creates a >> libasync_wmi_lib.so.0 and libasync_wmi_lib.so.0.0.1 that their python script >> would >> otherwise copy during its install routine (obviously I wrote a native rpm >> section for >> installation). >> >> Anyone know the naming convention associated with so's when they get >> compiled, >> what is the .0.1 extra file used for, they are slightly different. >> >> Thanks, >> jlc > > > Some reading for you: > > http://www.ibm.com/developerworks/library/l-shobj/ > > As Ljubomir said, libasync_wmi_lib.so.0 will be a symlink to > libasync_wmi_lib.so.0.0.1. You can use objdump to find the soname(s) for > shared objects, e.g: > > objdump -p /path/to/libasync_wmi_lib.so.0.0.1 | grep SONAME > > or just run ldconfig against them and observe what symlinks are created. > I forgot to say, wrt packaging, you should create the symlink(s) in the buildroot so that they are packaged rather than just running ldconfig in %post. That way, the symlinks are owned by the rpm package and won't be left dangling when the package is uninstalled. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Shared object packaging in rpm
On 25/06/11 02:15, Joseph L. Casale wrote: > I whipped up a quick spec to package Zenoss' wmi client and noticed it > creates a > libasync_wmi_lib.so.0 and libasync_wmi_lib.so.0.0.1 that their python script > would > otherwise copy during its install routine (obviously I wrote a native rpm > section for > installation). > > Anyone know the naming convention associated with so's when they get compiled, > what is the .0.1 extra file used for, they are slightly different. > > Thanks, > jlc Some reading for you: http://www.ibm.com/developerworks/library/l-shobj/ As Ljubomir said, libasync_wmi_lib.so.0 will be a symlink to libasync_wmi_lib.so.0.0.1. You can use objdump to find the soname(s) for shared objects, e.g: objdump -p /path/to/libasync_wmi_lib.so.0.0.1 | grep SONAME or just run ldconfig against them and observe what symlinks are created. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
