Ehhhh
I found a 5.8 (i686 though) box of mine still needing the sudo
update... I wasn't able to duplicate the behavior I saw with my other
server though.
I guess it was a fluke or somebody is messing with the server. ;)
---~~.~~---
Mike
// SilverTip257 //
On Wed, Jul 18, 2012 at 12:16 PM, SilverTip257 <silvertip257@xxxxxxxxx> wrote:
> The particular box I noticed the problem on is 5.8 x86_64
> Unfortunately I didn't think to gather much information ... I wanted
> to get my hosts backing up.
>
> No .rpmnew file - I know what you're referring to as I've seen them
> for other configs.
>
> ---~~.~~---
> Mike
> // SilverTip257 //
>
>
> On Wed, Jul 18, 2012 at 9:40 AM, John Doe <jdmls@xxxxxxxxx> wrote:
>> From: SilverTip257 <silvertip257@xxxxxxxxx>
>>
>>>This is a bit off-topic in relation to your original message, but
>>> related to the sudo update.
>>>
>>> On one of my hosts I have special allowances via sudoers in order to
>>> rsync while preserving permissions ... the sudo update whacked the
>>> lines for my backup hosts, but left the line for my wheel access in
>>> place.
>>
>> The update did not create a .rpmnew...?
>> Updating : sudo-1.7.4p5-11.el6.x86_64 165/447
>> warning: /etc/sudoers created as /etc/sudoers.rpmnew
>> It lead me to find out about the "new" sudoers.d directory (for 6.x).
>>
>> JD
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
