Rod,
Thanks for the quick reply. I have asked the
customer to make sure crle is not being invoked
in a startup script. If the file is being modified,
should they be able to ls -l on the file before
the shutdown and then ls -l (or something similar)
and compare to demonstrate the file is being
manipulated. Is there a way to track or identify who/what
may be modifying the file?
Thanks,
Dennis
On 09/11/08 11:17, Rod Evans wrote:
> Dennis P Van Eron wrote:
>> Hi ,
>> Please reply directly to me as I am not on this alias.
>> I have a customer that executes the following crle command
>>
>> crle -l /lib:/usr/lib:/usr/sfw/lib -s /opt/iplanet/ims-6.2/lib -u ?v
>> and when he excutes crle command he sees the following
>> # crle
>> Command line:
>> crle -c /var/ld/ld.config -l /lib:/usr/lib:/usr/sfw/lib -s
>> /lib/secure:/usr/lib/secure:/opt/iplanet/ims-6.2/lib
>>
>> So all looks ok?
>>
>> The he reboots the system and executes the crle command again
>> # crle
>> Command line:
>> crle -c /var/ld/ld.config -l /lib:/usr/lib:/usr/sfw/lib
>>
>> So it seems that the -s (Specify a new trusted directory)
>> works but is not persistent through a reboot.
>> Should it be?
>> Is this a bug?
>> Or is he executing the crle utility incorrectly.
>
> The only time a configuration file will change is when someone
> uses crle(1) to do it. And, there's nothing in a standard
> Solaris reboot (that I'm aware of) that would reset, or alter
> a configuration file.
>
> Are you sure someone hasn't added to a startup script a crle
> command that is simply setting /usr/sfw/lib and thus "overriding"
> your changes?
>
>
