Thanks, the selinux relabeling appears to have been it. Everything including
NetworkManager is back on track again!
Thank you very much for your patient efforts!!
Best wishes,
Ranjan
On Tue, 17 Mar 2020 20:35:49 -0700 Samuel Sieb wrote:
> On 3/17/20 8:18 PM, Ranjan Maitra wrote:
> > Hi, thank
On 3/17/20 8:18 PM, Ranjan Maitra wrote:
Hi, thanks. The wheel line reads:
wheel:x:10:username
So I guess it is there. However, I neither have sudo access or network manager.
Also, when I say
reboot,
That wasn't the command I gave you. It was:
/usr/sbin/reboot -f
But since you mentioned s
Hi, thanks. The wheel line reads:
wheel:x:10:username
So I guess it is there. However, I neither have sudo access or network manager.
Also, when I say
reboot,
I get:
Failed to connect to bus: Connection refused
Does this shed any light. Thanks!
Mar 17, 2020 10:11:16 PM Samuel Sieb :
> On
On 3/17/20 6:16 PM, Ranjan Maitra wrote:
My apologies, but I still don't have sudo access and I have now lost network
manager.
id says exactly the same thing as before except that there is no "7(lp)" before
the context field.
Did the usermod command not work? If you boot with the init=/bin
My apologies, but I still don't have sudo access and I have now lost network
manager.
id says exactly the same thing as before except that there is no "7(lp)" before
the context field.
My apologies again for any inclarity but because I am not on the network I
cannot cut and paste and have to
On 3/17/20 6:04 PM, Ranjan Maitra wrote:
Hi, your latest suggestion resulted in success at the terminal but I don't have
network manager anymore or sudo access. So I have also lost access to the
network. What should I try? Thanks again, Ranjan
You still don't have sudo access? What does the
Hi, your latest suggestion resulted in success at the terminal but I don't have
network manager anymore or sudo access. So I have also lost access to the
network. What should I try? Thanks again, Ranjan
___
users mailing list -- users@lists.fedoraproje
On 3/17/20 3:19 PM, Ranjan Maitra wrote:
On Tue, 17 Mar 2020 17:11:46 -0500 Ranjan Maitra wrote:
On Tue, 17 Mar 2020 14:53:26 -0700 Samuel Sieb wrote:
Since I'm not sure which rescue setup you have, I'll give you the easier
method. At the grub menu edit the boot entry and add "init=/bin/bash
On Tue, 17 Mar 2020 17:11:46 -0500 Ranjan Maitra wrote:
> Hi,
>
> I did this.
>
> On Tue, 17 Mar 2020 14:53:26 -0700 Samuel Sieb wrote:
>
> > On 3/17/20 2:34 PM, Ranjan Maitra wrote:
> > > On Tue, 17 Mar 2020 13:54:59 -0700 Samuel Sieb wrote:
> > >> Somehow you got dropped from the wheel group.
Hi,
I did this.
On Tue, 17 Mar 2020 14:53:26 -0700 Samuel Sieb wrote:
> On 3/17/20 2:34 PM, Ranjan Maitra wrote:
> > On Tue, 17 Mar 2020 13:54:59 -0700 Samuel Sieb wrote:
> >> Somehow you got dropped from the wheel group. Did you uncheck your
> >> administrator access in the user control pane
On 3/17/20 2:34 PM, Ranjan Maitra wrote:
On Tue, 17 Mar 2020 13:54:59 -0700 Samuel Sieb wrote:
Somehow you got dropped from the wheel group. Did you uncheck your
administrator access in the user control panel? In any case, if you
don't have another admin user, you will need to use a live or r
fter a while, I
> >>> finally rebooted and am on the 5.5.8-200.fc31.x86_64 kernel. However, I
> >>> appear to have lost my sudo access.
> >>>
> >>> I get: that my username "is not in the sudoers file. This incident will
> >>> be r
have
lost my sudo access.
I get: that my username "is not in the sudoers file. This incident will be
reported."
Not sure how this happened. How do I get back into sudoers? I am not even sure
I, (in fact I think that I do not), have a root account.
It's unlikely that you were ever
to have lost my sudo access.
> >
> > I get: that my username "is not in the sudoers file. This incident will be
> > reported."
> >
> > Not sure how this happened. How do I get back into sudoers? I am not even
> > sure I, (in fact I think that I do not
On 3/17/20 11:42 AM, Ranjan Maitra wrote:
I am on F31 and have always used sudo. This morning, after a while, I finally
rebooted and am on the 5.5.8-200.fc31.x86_64 kernel. However, I appear to have
lost my sudo access.
I get: that my username "is not in the sudoers file. This incident
Hello,
I am on F31 and have always used sudo. This morning, after a while, I finally
rebooted and am on the 5.5.8-200.fc31.x86_64 kernel. However, I appear to have
lost my sudo access.
I get: that my username "is not in the sudoers file. This incident will be
reported."
Not sur
Allegedly, on or about 14 June 2013, staticsafe sent:
> visudo does some syntax checks to check for errors in the edit.
As well as ensuring that your edits are accepted. It's possible to edit
the file, and thanks to the timing of when you did the edit, and other
things happening on the system, th
ngs when setting up the user accounts. And anyone who
was capable of putting themselves in the wheel group, would be just as
able to edit the sudoers file.
This is an alternative way of doing the same thing:
> What you need to do is insert the _following_ line, that looks like
> (in my cas
gt;> /etc/sudoers
>Where 'loginname' is your user account.
> easier for me, no need for that awful 'vi'
rghht. *or*,
gpasswd wheel -a loginname
which has no need for vi *and* doesn't risk clobbering your sudoers file
with a typo.
--
Matthew Miller ☁
Am 14.06.2013 20:51, schrieb Steven Stern:
> On 06/14/2013 01:43 PM, Matthew Miller wrote:
>> On Fri, Jun 14, 2013 at 01:04:13PM -0400, Doug wrote:
>>> ## Allows people in group wheel to run all commands
>>> %wheel ALL=(ALL) ALL
> This line *IS* uncommented by default.
from:
http://www.mjmwired.net/resources/mjm-fedora-f17.html
Personal Fedora 17 Installation Guide
by Mauriat Miranda (http://www.mjmwired.net/contact/)
echo 'loginname ALL=(ALL) ALL' >> /etc/sudoers
Where 'loginname' is your user account.
easier for me, no need for that awful 'vi'
On 06/14/2013 01:04 PM, Matthew Miller wrote:
Oh no. Start with 'sudo bash' or 'sudo su'. People do this all the time.
Then `unset HISTFILE`. Then do the above not with sudo.
But this is very off-topic.
It is and it isn't. If nothing else, it makes it clear just how easy it
is to gain un-log
On Fri, Jun 14, 2013 at 12:21:44PM -0700, Joe Zeff wrote:
> > sudo cp /bin/bash /bin/mylocalshell
> > sudo mylocalshell
> >I know this is preventable, but it's something to think about. No one
> >should have sudo who you would not trust with root itself. sudo just
> >adds a layer of accountabil
On 06/14/2013 11:51 AM, Steven Stern wrote:
OK, let's now have some fun
sudo cp /bin/bash /bin/mylocalshell
sudo mylocalshell
I know this is preventable, but it's something to think about. No one
should have sudo who you would not trust with root itself. sudo just
adds a layer of acco
On Fri, Jun 14, 2013 at 01:51:42PM -0500, Steven Stern wrote:
> >> %wheel ALL=(ALL) ALL
> This line *IS* uncommented by default.
> >>> Hmmm... Maybe it's been so long since I've had to do it. In any case,
> >>> it was commented on the two CentOS 6 systems I just set up.
> >> In m
On 06/14/2013 01:43 PM, Matthew Miller wrote:
> On Fri, Jun 14, 2013 at 01:04:13PM -0400, Doug wrote:
>> ## Allows people in group wheel to run all commands
>> %wheel ALL=(ALL) ALL
This line *IS* uncommented by default.
>>> Hmmm... Maybe it's been so long since I've had to d
On Fri, Jun 14, 2013 at 01:04:13PM -0400, Doug wrote:
> ## Allows people in group wheel to run all commands
> %wheel ALL=(ALL) ALL
> >>This line *IS* uncommented by default.
> >Hmmm... Maybe it's been so long since I've had to do it. In any case,
> >it was commented on the two
On 06/14/2013 12:42 PM, Steven Stern wrote:
On 06/14/2013 08:11 AM, Matthew Miller wrote:
remove the comment before the 2nd line here so it looks like this:
## Allows people in group wheel to run all commands
%wheel ALL=(ALL) ALL
This line *IS* uncommented by default.
Hmmm... M
On 06/14/2013 08:11 AM, Matthew Miller wrote:
>> remove the comment before the 2nd line here so it looks like this:
>> > ## Allows people in group wheel to run all commands
>> > %wheel ALL=(ALL) ALL
> This line *IS* uncommented by default.
>
Hmmm... Maybe it's been so long since I've h
z.By terminal, when I copied
> >the file of libflashplayer.so to /usr/lib64/mozilla/plugins,the result
> >is my user name is not in the file of sudoers.Except C Language,I do not
> >know any more about computer:BY TERMINAL,I NEED THE DETAIL OPERATE
> >PROCESS ABOUT EDITING SUD
On Fri, Jun 14, 2013 at 11:25:39AM -0400, Doug wrote:
> While you are "supposed" to use visudo to edit sudoers, that
> requires that you know how to use the vi editor. Visudo is designed
> to catch mistakes that you make. However, you can edit sudoers with
> any editor; it is only a text file and d
/plugins,the result
is my user name is not in the file of sudoers.Except C Language,I do not
know any more about computer:BY TERMINAL,I NEED THE DETAIL OPERATE
PROCESS ABOUT EDITING SUDOERS FILE--EVEN EVERY COMMAND
While you are "supposed" to use visudo to edit sudoers, that requires
that yo
as root:
gpasswd wheel -a sdstern
Or, you can use the GUI user admin tool to do the same thing.
So, you *don't need to edit the file directly, which is good thing, because
the sudoers file has a complicated and fussy syntax.
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁
--
users m
ib64/mozilla/plugins,the result
> is my user name is not in the file of sudoers.Except C Language,I do not
> know any more about computer:BY TERMINAL,I NEED THE DETAIL OPERATE
> PROCESS ABOUT EDITING SUDOERS FILE--EVEN EVERY COMMAND
>
As root, type
visudo
remove the comment before
r.so to /usr/lib64/mozilla/plugins,the result
> is my user name is not in the file of sudoers.Except C Language,I do not
> know any more about computer:BY TERMINAL,I NEED THE DETAIL OPERATE
> PROCESS ABOUT EDITING SUDOERS FILE--EVEN EVERY COMMAND
>
You could try copying it just for y
file of sudoers.Except C Language,I do not
know any more about computer:BY TERMINAL,I NEED THE DETAIL OPERATE
PROCESS ABOUT EDITING SUDOERS FILE--EVEN EVERY COMMAND
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org
On 11/01/12 23:58, Kaushal Shriyan wrote:
Hi,
Any documentation to set up sudoers file apart from man sudoers ?
Regards,
Kaushal
This link gives an example,
with comments as to what each user
may need to do.
http://www.gratisoft.us/sudo/sample.sudoers
--
Regards,
Frank Murphy
UTF_8
On Thu, 2012-01-12 at 05:28 +0530, Kaushal Shriyan wrote:
> Hi,
>
>
> Any documentation to set up sudoers file apart from man sudoers ?
Take a look in /usr/share/doc/sudo*
Several examples, read-mes etc.
--
Best Regards
Peter Larsen
Wise words of the day:
* Jes wonders
On 1/11/12, Kaushal Shriyan wrote:
> Hi,
>
> Any documentation to set up sudoers file apart from man sudoers ?
>
> Regards,
>
> Kaushal
>
Try the following website..
http://www.gratisoft.us/sudo/sudoers.man.html
HTH
Marvin
--
users mailing list
users@lists.fedorapr
On Thu, Jan 12, 2012 at 7:58 AM, Kaushal Shriyan
wrote:
> Any documentation to set up sudoers file apart from man sudoers ?
Maybe you can refer to the /etc/sudoers itself, there are some examples in
it.
cat /etc/sudoers, which needs root priviledge.
--
users mailing list
us
Hi,
Any documentation to set up sudoers file apart from man sudoers ?
Regards,
Kaushal
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki
41 matches
Mail list logo
