DSET 3.2: OS detection, SFCB service mandatory

Gaash Hazan gaash at qwilt.com
Wed Jul 11 21:24:17 CDT 2012

I have another issue with DSET 3.2 as well.

Even when DSET is executed by root, DSET prompts for root password.
This prevents any kind of running DSET automatically (e.g. by cron)

Hope it will be fixed soon.


Gaash Hazan
Qwilt | M +972.54.4575.232 | gaash at qwilt.com

On Thu, Jul 12, 2012 at 5:00 AM, Howell, Andrew
<Andrew.Howell at woodside.com.au> wrote:
> I had two issues with DSET as well.
> 1. The same /etc/issue problem. We like many people probably modify /etc/issue in our SOE so using it to detect OS version isn't really a good idea. Dell should use lsb_release and OS specific files like /etc/redhat-release instead.
> 2. The much worse issue I came across when running DSET in the run once (not install) mode was that it modified system libraries and left them in a broken state.
> It changes the /usr/lib64/libssl.so.10 symlink from pointing to libssl.so.1.0.0 to libssl.so.6. This causes any program linked to libssl 1.0 to now segfault.
> A run once program like this should either request you have certain library versions installed, or it should be statically linked. It shouldn't modify system libraries and certainly not leave those modifications in place after it's finished running.
> This is unbelievable behaviour for a diagnostics program which we should be able to safely run on production systems.
> Andrew
> Andrew Howell
> Unix System Administrator
> IT Infrastructure
> Woodside Energy Ltd.
> Woodside Plaza
> 240 St Georges Terrace
> Perth WA 6000
> Australia
> T: +61 8 9348 3863
> F: +61 8 9348 6644
> E: andrew.howell at woodside.com.au
> -----Original Message-----
> From: linux-poweredge-bounces at dell.com [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Giulio
> Sent: Wednesday, 11 July 2012 9:57 PM
> To: linux-poweredge at dell.com
> Subject: DSET 3.2: OS detection, SFCB service mandatory
> PE-T620, CENTOS 6.x 2.6.32-220.23.1.el6.x86_64
> I'm running DSET 2.2 and I realized DSET 3.2 is available on Dell web site.
> I had 2 issues with DSET 3.2 install:
> When trying to instal DSET there's a new OS detection
>         OS_NAME1=`cat /etc/issue | grep ESX`
>         OS_NAME2=`cat /etc/issue | grep SUSE`
>         OS_NAME3=`cat /etc/issue | grep Red`
> Since we use CentOS, I had already rewritten /etc/redhat-release to match
> what OMSA and other Dell software expect to find in it.
> But now DSET looks at /etc/issue instead of /etc/redhat-release,
> unfortunately we customize /etc/issue and it doesn't contain "Red Hat" or
> "CentOS" strings.
> Is looking at /etc/issue the new way all Dell software will use for OS
> detection going forward?
> 2) New service mandatory:
> Upon install this is printed on the screen:
>         The Small Footprint CIM Broker (SFCB) is a network service that enables
>         remote collection of system configuration information.
>         To perform the option that you selected, it is necessary to install and
>         start this service and leave it running in background for future
>         configuration collection
>         Continue installing/activating the SFCB on this system to listen for
>         incoming collection requests from clients.
> Old versions of DSET would allow you to just run the diagnostics to send the
> zip file to Dell support w/o installing anything permanent; the new version
> not only didn't allow me to do that, but it wants to install a permanent
> service (I already have OMSA 7 installed with its services running).
> Is this new DSET service really necessary?
> Thanks
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge
> NOTICE: This email and any attachments are confidential.
> They may contain legally privileged information or
> copyright material. You must not read, copy, use or
> disclose them without authorisation. If you are not an
> intended recipient, please contact us at once by return
> email and then delete both messages and all attachments.
> _______________________________________________
> Linux-PowerEdge mailing list
> Linux-PowerEdge at dell.com
> https://lists.us.dell.com/mailman/listinfo/linux-poweredge

More information about the Linux-PowerEdge mailing list