previously on this list ubuntu-devel-discuss-requ...@lists.ubuntu.com
contributed:
> > Then a patch to visudo is due so it knows about files in /etc/sudoers.d and
> > to also allow you to save "partials" to that location... **hint**
>
> If the goal an intact default configuration file, keep it
On 17/05/2014 14:11, Dimitri John Ledkov wrote:
> Whilst coding you may want to open up /dev/port, e.g.
> $ sudo chmod g+w /dev/port # if you need r/w access
> $ sudo adduser `id -un` kmem
> (re-login)
>
> This will open up /dev/port for r+w to yourself (well anyone in kmem
> group). This is slight
On 17 May 2014 06:53, Charl Wentzel wrote:
> On 17/05/2014 01:35, Dimitri John Ledkov wrote:
>
>> On 16 May 2014 07:26, Charl Wentzel wrote:
>
>>> I wanted do to debugging in Eclipse which required me to let Eclipse run
>>> gdb with sudo. However, for this to work, sudo must not ask for a
>>> pa
On 17/05/2014 01:35, Dimitri John Ledkov wrote:
> On 16 May 2014 07:26, Charl Wentzel wrote:
>> I wanted do to debugging in Eclipse which required me to let Eclipse run
>> gdb with sudo. However, for this to work, sudo must not ask for a
>> password. So I've added the following entry in /etc/s
On 16 May 2014 07:26, Charl Wentzel wrote:
> Hi Guys
>
> I recently struggled with an issue for quite a few days because of the
> way the /etc/sudoers file is laid out. I would like to make a
> suggestion to change it that would hopefully save others the same hassle.
>
> I wanted to debugging in
On 05/16/2014 04:07 PM, Mike Miller wrote:
> On Fri, May 16, 2014 at 10:23:09 +0200, Tamas Papp wrote:
>> If you edit sudoers via visudo there is a syntax checking.
>> If you do something wrong in /etc/sudoers.d/a, there is no syntax
>> checking and the your user gets locked out:
> So edit /etc/su
On 05/16/2014 04:02 PM, Luis Mondesi wrote:
>> On May 16, 2014, at 9:54, Tamas Papp wrote:
>>
>>
>> On 05/16/2014 03:50 PM, Luis Mondesi wrote:
On May 16, 2014, at 4:23, Tamas Papp wrote:
> On 05/16/2014 09:19 AM, Andrea Corbellini wrote:
> Actually, you are supposed to cr
On Fri, May 16, 2014 at 10:23:09 +0200, Tamas Papp wrote:
> If you edit sudoers via visudo there is a syntax checking.
> If you do something wrong in /etc/sudoers.d/a, there is no syntax
> checking and the your user gets locked out:
So edit /etc/sudoers.d/a with visudo:
visudo -f /etc/sudoers
> On May 16, 2014, at 9:54, Tamas Papp wrote:
>
>
> On 05/16/2014 03:50 PM, Luis Mondesi wrote:
>>> On May 16, 2014, at 4:23, Tamas Papp wrote:
>>>
>>>
On 05/16/2014 09:19 AM, Andrea Corbellini wrote:
Actually, you are supposed to create a new file in /etc/sudoers.d for
custom
On 05/16/2014 03:50 PM, Luis Mondesi wrote:
>> On May 16, 2014, at 4:23, Tamas Papp wrote:
>>
>>
>>> On 05/16/2014 09:19 AM, Andrea Corbellini wrote:
>>> Actually, you are supposed to create a new file in /etc/sudoers.d for
>>> custom rules. You shouldn't edit /etc/sudoers directly; this will
>>>
> On May 16, 2014, at 4:23, Tamas Papp wrote:
>
>
>> On 05/16/2014 09:19 AM, Andrea Corbellini wrote:
>> Actually, you are supposed to create a new file in /etc/sudoers.d for
>> custom rules. You shouldn't edit /etc/sudoers directly; this will
>> ensure that package upgrades can happen without
On 05/16/2014 09:19 AM, Andrea Corbellini wrote:
> Actually, you are supposed to create a new file in /etc/sudoers.d for
> custom rules. You shouldn't edit /etc/sudoers directly; this will
> ensure that package upgrades can happen without asking you any
> question about the changes you made to tha
On Fri, May 16, 2014 at 8:26 AM, Charl Wentzel
wrote:
Hi Guys
I recently struggled with an issue for quite a few days because of the
way the /etc/sudoers file is laid out. I would like to make a
suggestion to change it that would hopefully save others the same
hassle.
I wanted to debugging
13 matches
Mail list logo
