o auto-mount at login with the /dev/sdc7
/dev/sde1 devices auto- mounting on attach. The device that the sudo
password is prompted for is being mounted in folder /run/media/steve.
It's probably random which one is discovered first. If you give the
password, do they both get mounted?
No, on
ev/sdc7 /dev/sde1 devices auto-
mounting on attach. The device that the sudo password is prompted for is
being mounted in folder /run/media/steve.
It's probably random which one is discovered first. If you give the
password, do they both get mounted?
--
lume being mounted seems to change
between /dev/sdc7 and /dev/sde1 each time I boot. I've found what it is.
In the device auto mount system settings I've set all "Attached Devices"
to auto-mount at login with the /dev/sdc7 /dev/sde1 devices
auto-mounting on attach. The de
On 10/14/24 2:03 PM, Stephen Morris via users wrote:
Hi,
For some reason when I start KDE I am being prompted for
credentials to mount /dev/sdc7, but there is no entry in /etc/fstab for
the UUID of that volume. Where is the prompt coming from? I think /dev/
sdc7 is my Ubuntu boot partitio
Hi,
For some reason when I start KDE I am being prompted for
credentials to mount /dev/sdc7, but there is no entry in /etc/fstab for
the UUID of that volume. Where is the prompt coming from? I think
/dev/sdc7 is my Ubuntu boot partition.
Below is my /etc/fstab:
UUID=b1b1448c-3e41-47a6
On Sat, Dec 30, 2023 at 11:48:31PM -0500, Robert McBroom via users wrote:
On 12/30/23 18:18, Mike Wright wrote:
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set.
On 12/30/23 20:48, Robert McBroom via users wrote:
On 12/30/23 18:18, Mike Wright wrote:
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root
owns the file and
On 12/30/23 18:18, Mike Wright wrote:
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root
owns the file and is 0. Looking at a working system directory list
Robert McBroom via users writes:
On a system restore from a tar archive sudo won't work. Says /usr/bin/sudo
needs to be owned by 0 with the suid bit set. Root owns the file and is 0.
Looking at a working system directory list shows
-rwsr-xr-x. 1 root root 57456 Aug 16 20:
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root owns
the file and is 0. Looking at a working system directory list shows
-rwsr-xr-x. 1 root root
On 12/30/23 15:13, Robert McBroom via users wrote:
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root owns
the file and is 0. Looking at a working system directory list shows
-rwsr-xr-x. 1 root root
On a system restore from a tar archive sudo won't work. Says
/usr/bin/sudo needs to be owned by 0 with the suid bit set. Root owns
the file and is 0. Looking at a working system directory list shows
-rwsr-xr-x. 1 root root 57456 Aug 16 20:00 su
---s--x--x. 1 root root 2
On 10/05/2023 12:20 PM, old sixpack13 wrote:
KISS
bash history
CRTL+r and keyed in "ether" and ENTER
thanks anyway !
That works, of course, if the line you need to repeat is different every
time. If it's something you use all the time, either a one-liner
script, or an alias in .bashrec migh
> On 10/03/2023 03:35 PM, old sixpack13 wrote:
>
> If you're using that exact same command often enough, create an alias
> for it and put it into your .bashrc. That way, you not only save
> keystrokes, you avoid typoes.
KISS
bash history
CRTL+r and keyed in "ether" and ENTER
thanks anyway !
_
> On 3 Oct 2023, at 22:15, old sixpack13 wrote:
>
> I don't want to have user joe in sudo group
Why not? You can control who runs which command with sudoers config.
Barry
___
users mailing list -- users@lists.fedoraproject.org
To un
On 10/03/2023 03:35 PM, old sixpack13 wrote:
I've tested similar.
If you're using that exact same command often enough, create an alias
for it and put it into your .bashrc. That way, you not only save
keystrokes, you avoid typoes.
___
users mailin
> On 10/3/23 14:35, old sixpack13 wrote:
>
> Add "-P" to the "su" command.
Thanks again and @ALL
the working command is:
su -P -c "sudo ether-wake -i enp3s0 && ping nuc" - ron
___
users mailing list
On 10/3/23 14:35, old sixpack13 wrote:
On 10/3/23 14:14, old sixpack13 wrote:
su -c "sudo ether-wake -i enp3s0 && ping nuc" - ron
Thanks !
I've tested similar.
with your command I get:
Password:
sudo: a terminal is required to read the password; either use the
> On 10/3/23 14:14, old sixpack13 wrote:
>
> su -c "sudo ether-wake -i enp3s0 && ping nuc" - ron
Thanks !
I've tested similar.
with your command I get:
Password:
sudo: a terminal is required to read the password; either use the -S option to
read from standa
On 10/3/23 14:14, old sixpack13 wrote:
I have the following problem:
I'm logged in as user joe (he is not in sudo group) and want to etherwake a
remote box, called nuc, via an one-liner in an script.
now, on an command line, I usually do
1. su - ron (ron is in sudo group)
2. and then
On 10/3/23 14:20, Joe Zeff wrote:
On 10/03/2023 03:14 PM, old sixpack13 wrote:
now, on an command line, I usually do
1. su - ron (ron is in sudo group)
2. and then sudo ether-wake -i enp3s0 && ping nu
Why? If you have access to su and the root password, why bother with
sudo? Jus
On 10/03/2023 03:14 PM, old sixpack13 wrote:
now, on an command line, I usually do
1. su - ron (ron is in sudo group)
2. and then sudo ether-wake -i enp3s0 && ping nu
Why? If you have access to su and the root password, why bother with
sudo? Just use su -c "ether-wake -i enp3s
I have the following problem:
I'm logged in as user joe (he is not in sudo group) and want to etherwake a
remote box, called nuc, via an one-liner in an script.
now, on an command line, I usually do
1. su - ron (ron is in sudo group)
2. and then sudo ether-wake -i enp3s0 && ping n
On Thu, 27 Apr 2023 01:18:50 -0400
Jeffrey Walton wrote:
> Hi Everyone,
>
> I dnf-system-upgraded my last machine from F37 to F38. I screwed up at
> post-upgrade at 'sudo rpmconf -a'.
[snip]
> How do I restart rpmconf?
I don't know if this will work, but you coul
On Thu, Apr 27, 2023 at 1:41 AM Samuel Sieb wrote:
>
> On 4/26/23 22:18, Jeffrey Walton wrote:
> > I dnf-system-upgraded my last machine from F37 to F38. I screwed up at
> > post-upgrade at 'sudo rpmconf -a'.
> >
> > I saw a message in the terminal:
On 4/26/23 22:18, Jeffrey Walton wrote:
I dnf-system-upgraded my last machine from F37 to F38. I screwed up at
post-upgrade at 'sudo rpmconf -a'.
I saw a message in the terminal:
Broadcast message from gdm@callboot on tty1 (Thu 2023-04-27 01:09:53 EDT):
The system will s
Hi Everyone,
I dnf-system-upgraded my last machine from F37 to F38. I screwed up at
post-upgrade at 'sudo rpmconf -a'.
I saw a message in the terminal:
Broadcast message from gdm@callboot on tty1 (Thu 2023-04-27 01:09:53 EDT):
The system will suspend now!
And I pressed ENTER
On Fri, Dec 30, 2022 at 3:42 PM Samuel Sieb wrote:
> On 12/30/22 08:13, Geoffrey Leach wrote:
> > I'd appreciate any suggestions of a workaround for this situation.
> > Works fine without the "sudo". It also fails when run in ~root
> >
> > sudo mpg123 t
You really really really shouldn't play audio/video under sudo (or browse the
web or whatever). Please don't. sudo (as the root account) is meant to be used
for system administration only, i.e. stuff like `dnf install blabla` or `vim
/etc/[some config file]`. For almost everything
On Fri, 30 Dec 2022 11:41:58 -0800
Samuel Sieb wrote:
> On 12/30/22 08:13, Geoffrey Leach wrote:
> > I'd appreciate any suggestions of a workaround for this situation.
> > Works fine without the "sudo". It also fails when run in ~root
> >
> > sudo mpg
On 12/30/22 08:13, Geoffrey Leach wrote:
I'd appreciate any suggestions of a workaround for this situation.
Works fine without the "sudo". It also fails when run in ~root
sudo mpg123 t.mp3
Why are you trying to run it with sudo?
__
On Fri, 30 Dec 2022 08:46:40 -0800
"Doug Herr" wrote:
> On Fri, Dec 30, 2022, at 8:13 AM, Geoffrey Leach wrote:
> > I'd appreciate any suggestions of a workaround for this situation.
> > Works fine without the "sudo". It also fails when run in ~root
> &
On Fri, Dec 30, 2022, at 8:13 AM, Geoffrey Leach wrote:
> I'd appreciate any suggestions of a workaround for this situation.
> Works fine without the "sudo". It also fails when run in ~root
>
> sudo mpg123 t.mp3
I think that is considered a feature and not a bug,
I'd appreciate any suggestions of a workaround for this situation.
Works fine without the "sudo". It also fails when run in ~root
sudo mpg123 t.mp3
High Performance MPEG 1.0/2.0/2.5 Audio Player for Layers 1, 2 and 3
version 1.31.1; written and copyright by Michael
I'm embarrassed. O well,, at least i have it right now :-(
On Sat, Nov 19, 2022 at 8:52 PM Geoffrey Leach
wrote:
> sorry, i don't understand the question. the goal is for a normal user to
> be able
> O bother. I see what I'm doing. I must say 'sudo ...'
sorry, i don't understand the question. the goal is for a normal user to be
able
O bother. I see what I'm doing. I must say 'sudo ...' before the command.
Sorry for the confusion.
On Sat, Nov 19, 2022 at 8:45 PM Slade Watkins via users <
users@lists.fedoraproject.org
On 11/19/22 20:37, Geoffrey Leach wrote:
Yet the simplest test fails:
geoff@webster[95] ~: touch /foo
touch: cannot touch '/foo': Permission denied
You have to actually *use* sudo...
e.g. "sudo touch /foo"
___
users m
On Sat, Nov 19, 2022 at 9:14 PM Geoffrey Leach wrote:
>
> any suggestion as what might be my probem (yes, change made with visudo)
>
What's going on?
-srw
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le.
that everything is set up correctly,
geoff@webster[94] ~: sudo -l
Matching Defaults entries for geoff on webster:
always_set_home, match_group_by_gid, always_query_group_plugin,
env_reset,
env_keep="COLORS DISPLAY HOSTNAME HISTSIZE KDEDIR LS_COLORS",
env_keep+="MAIL QTDI
Geoffrey Leach writes:
any suggestion as what might be my probem (yes, change made with visudo)
Perhaps if you try to actually describe what your problem is, someone might
be able to figure it out for you.
But merely stating that you have some kind of a "problem with sudo" is
any suggestion as what might be my probem (yes, change made with visudo)
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en
st"
4. Copy the line that has "/unix:", all three parts
5. Use su - or sudo to get an interactive session for alternate user
6. Run xauth command with no arguments
7. Type "list" at the prompt
8. Assuming this user currently doesn't have permission (no entry for
host/di
ot;, all three parts
5. Use su - or sudo to get an interactive session for alternate user
6. Run xauth command with no arguments
7. Type "list" at the prompt
8. Assuming this user currently doesn't have permission (no entry for
host/display):
9. Type "add" and then paste the l
", all three parts
5. Use su - or sudo to get an interactive session for alternate user
6. Run xauth command with no arguments
7. Type "list" at the prompt
8. Assuming this user currently doesn't have permission (no entry for
host/display):
9. Type "add" and then paste
Hi L,
> How do you get your Firefox to run/work with different user?
> I'm thinking obvious - sudo, su - kind of 'runas' with
> windows OS.
Seeing as no-one has said this, yet:
*** Running things as root is ill-advised. ***
While running a file manager as root to
For root run GUI apps in KDE, I use kdesu.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
L
Making some assumptions about your requirements:
1. Make sure xauth is installed
2. Your DISPLAY environment variable is likely: ":0" - just verify it is set
3. Run the command: "xauth list"
4. Copy the line that has "/unix:", all three parts
5. Use su - or sudo to
unar
This runs the Xfce program that acts as a GUI sudo which then runs my
file manager. Replace that with whatever program your DE provides.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to user
On 11/01/2022 17:32, Robert Moskowitz wrote:
On 1/11/22 12:23, lejeczek via users wrote:
Hi guys.
How do you get your Firefox to run/work with different user?
I'm thinking obvious - sudo, su - kind of 'runas' with
windows OS.
Kludge I have used for some apps, notably my f
On 1/11/22 12:23, lejeczek via users wrote:
Hi guys.
How do you get your Firefox to run/work with different user?
I'm thinking obvious - sudo, su - kind of 'runas' with windows OS.
Kludge I have used for some apps, notably my file browser to run as root
is to:
in Termina
Hi guys.
How do you get your Firefox to run/work with different user?
I'm thinking obvious - sudo, su - kind of 'runas' with
windows OS.
many thanks, L
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an em
Hi all,
Since upgrading to Fedora 35 sssd+sudo+gssapi no longer works. In
/etc/sssd/conf:
pam_gssapi_services = sudo, sudo-i
In /etc/pam.d/sudo:
#%PAM-1.0
auth sufficient pam_sss_gss.so
auth include system-auth
account include system-auth
password include system-auth
session optional
Apologies... got mixed up on this fedorahosted web interface.. this was meant
for sssd-users
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs
On 1/19/21 8:34 AM, Judd Gaddie wrote:
Hi, We have noticed a performance regression on some of our boxes when we upgraded
from Ubuntu 18.04 (sssd 1.16.1-1ubuntu1.7) (sudo 1.8.21p2) -> Ubuntu 20.04
(sssd 2.2.3-3ubuntu0.1) (sudo 1.8.31) (however it was not universal, some Ubuntu
20.04 boxes
On Tue, 2021-01-19 at 15:34 +, Judd Gaddie wrote:
> Hi, We have noticed a performance regression on some of our boxes when we
> upgraded from Ubuntu 18.04 (sssd 1.16.1-1ubuntu1.7) (sudo 1.8.21p2) -> Ubuntu
> 20.04 (sssd 2.2.3-3ubuntu0.1) (sudo 1.8.31) (however it was not univer
Hi, We have noticed a performance regression on some of our boxes when we
upgraded from Ubuntu 18.04 (sssd 1.16.1-1ubuntu1.7) (sudo 1.8.21p2) -> Ubuntu
20.04 (sssd 2.2.3-3ubuntu0.1) (sudo 1.8.31) (however it was not universal, some
Ubuntu 20.04 boxes are fine) joined to a FreeIPA domain.
, that isn't adding a user, it's
replacing the group list completely. You need the "-a" option to add a
group. When you ran that command, you removed yourself from the wheel
group which removed your sudo access.
___
users m
ater I added it , and this wast enough to gain again the sudo privileges..
Probably the cancellation was caused by the command
Now the problem is solved, as well it seems me strange that adding a new
group to a user should delete it from the list of sudoers
Again thank you to all that tried to hel
e suggestion to register
>> myself in the "audio group" ..
>> I made it using these commands:
>>
>> sudo adduser audio
>
>
> This should have given a usage error:
>
> Usage: adduser [options] LOGIN
>adduser -D
>adduser -D [option
On Sun, 27 Dec 2020 at 05:32, Angelo Moreschini
wrote:
> Hi
>
> some days before, I had a problem about using the *"beep" function..*
> ... working around, to solve my problem, I got the suggestion to register
> myself in the "audio group" ..
> I made it u
Hi
some days before, I had a problem about using the *"beep" function..*
... working around, to solve my problem, I got the suggestion to register
myself in the "audio group" ..
I made it using these commands:
*sudo adduser audio*
and also :
*sudo usernod -G audio *
Actu
On 3/30/20 10:40 PM, David wrote:
On the virus-front,
Regarding your non-Fedora "On the virus front"
Repulsive beyond belief and, more to the point, having nothing to do
with Fedora or any flavor on Linux
Shame
___
users mailing list -- users@li
To the few of you who recommended that I do a reinstall, to fix my sudo
problem, I just wanted you to know that the marvelous Fedora self-healed
itself.
I assume something in systemd update yesterday, or kernel rc7, fixed the
issue
that I was having.
Anyways, yesterday's update of system
Hi.
On Tue, 04 Feb 2020 12:25:39 -0800 Mike Wright wrote:
> launching an xterm from the cli then entering in the new xterm:
> lxc list
> and I get a password prompt. Absolutely no clue.
I think you should call:
sudo lxc list
or there is some magic to call sudo in you
On Tue, 4 Feb 2020 14:57:31 -0800
Mike Wright wrote:
> lxc-* files are from the original LXC. lxc is the base command for
> LXD which is based on LXC.
So, a naive guess that was wrong. :-) Thanks for the info.
___
users mailing list -- users@lists
On 2/4/20 1:10 PM, Earl Ramirez wrote:
On Tue, 2020-02-04 at 12:25 -0800, Mike Wright wrote:
# Cmnd alias specification
Cmnd_Alias LXC=/usr/bin/lxc
# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL
# Allow members of group sudo to execute any command
%sudo ALL
privileges
%admin ALL=(ALL) ALL
# Allow members of group sudo to execute any command
%sudo ALL=(ALL:ALL) ALL
# User privilege specification
root ALL=(ALL:ALL) ALL
mike ALL=(ALL) NOPASSWD:LXC
sudoers.d is empty
launching an xterm from the cli then entering in the new xterm:
lxc l
privileges
> %admin ALL=(ALL) ALL
>
> # Allow members of group sudo to execute any command
> %sudo ALL=(ALL:ALL) ALL
>
> # User privilege specification
> root ALL=(ALL:ALL) ALL
> mike ALL=(ALL) NOPASSWD:LXC
>
>
>
> sudoers.d is empty
>
> launch
On Tue, 2020-02-04 at 12:25 -0800, Mike Wright wrote:
> # Cmnd alias specification
> Cmnd_Alias LXC=/usr/bin/lxc
>
> # Members of the admin group may gain root privileges
> %admin ALL=(ALL) ALL
>
> # Allow members of group sudo to execute any command
> %sudo ALL=(
’, ‘)’) is optional.
And FWIW, I have working rules with and without spaces¹.
My bet is on another rule interfering, due to user mike
being in group admin or sudo. I've run into that myself.
¹ Because the rules were added at different times by
different people, not because I like to have me
in a list as well as
> special syntactic characters in a User Specification
> (‘=’, ‘:’, ‘(’, ‘)’) is optional.
>
> And FWIW, I have working rules with and without spaces¹.
>
> My bet is on another rule interfering, due to user mike
> being in group admin or sudo. I'
s with and without spaces¹.
My bet is on another rule interfering, due to user mike
being in group admin or sudo. I've run into that myself.
¹ Because the rules were added at different times by
different people, not because I like to have messy white
space. ;
.
It may be that you're hitting another rule which supercedes
the one you've got there (for example, if there's a rule
matching a group you're in). Using `sudo -U mike -ll` might
be helpful.
+1 for Todd's comments, I have added a couple of commands and I was
able to
On 20-02-03 16:23:07, Mike Wright wrote:
...
I am befuddled. Here is my sudoers file:
Defaultsenv_reset
Defaultsmail_badpass
Defaultssecure_path=
Cmnd_Alias LXC=/usr/bin/lxc
rootALL=(ALL:ALL) ALL
mikeALL=(ALL) NOPASSWD:LXC
%admin ALL=(ALL) ALL
%sudo ALL
other rule which supercedes
the one you've got there (for example, if there's a rule
matching a group you're in). Using `sudo -U mike -ll` might
be helpful.
+1 for Todd's comments, I have added a couple of commands and I was able
to access those commands without being prompt
hitting another rule which supercedes
>
> the one you've got there (for example, if there's a rule
>
> matching a group you're in). Using `sudo -U mike -ll` might
>
> be helpful.
+1 for Todd's comments, I have added a couple of commands and I was
abl
Hi,
Mike Wright wrote:
> I would like to execute a command using sudo and not have to provide a
> password. After much manpage time I added this:
>
> mikeALL=(ALL) NOPASSWD: /usr/bin/lxc
>
> In theory this allows mike, from any and all hosts, to execute wi
Hi Masters,
I would like to execute a command using sudo and not have to provide a
password. After much manpage time I added this:
mikeALL=(ALL) NOPASSWD: /usr/bin/lxc
In theory this allows mike, from any and all hosts, to execute
without a password.
Nonetheless, "mike"
don't know if due to changing hostname from the
default localhost.localdomain that had been set, or due to applied updates,
I had strange problems with latencies in sudo responses with great amount
of time before asking the password prompt and also when opening menus in
gnome, eg settings (ab
On 1/9/19 1:13 AM, Patrick Dupre wrote:
>
>> On 1/8/19 8:38 AM, Ulf Volmer wrote:
>>> On 08.01.19 10:57, Patrick Dupre wrote:
>>>
>>>> With visudo, I did
>>>> pdupre localhost=/usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB/
>>>
On 09.01.19 10:13, Patrick Dupre wrote:
>> $ mount /mnt/USB
>
> The problem is that it tries to mount at boot even if the drive is off
Add noauto as option to your fstab line.
This and other options are documented in 'man fstab'.
best regards
Ulf
> On 1/8/19 8:38 AM, Ulf Volmer wrote:
> > On 08.01.19 10:57, Patrick Dupre wrote:
> >
> >> With visudo, I did
> >> pdupre localhost=/usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB/
> >
> >> sudo /usr/bin/mount /dev/mapper/VolGrpUsr_DK0-
On 1/8/19 12:14 PM, Joe Zeff wrote:
On 01/08/2019 12:23 PM, Samuel Sieb wrote:
What does the "hostname" command give you? I would suggest using
"ALL" instead.
Not a good idea unless you really trust that user. This lets that
person mount this partition when needed and nothing else. (It m
On 01/08/2019 12:23 PM, Samuel Sieb wrote:
What does the "hostname" command give you? I would suggest using "ALL"
instead.
Not a good idea unless you really trust that user. This lets that
person mount this partition when needed and nothing else. (It might be
a good idea to allow umount
On 1/8/19 11:21 AM, Rick Stevens wrote:
On 1/8/19 10:58 AM, Patrick Dupre wrote:
sudo -l
[sudo] password for pdupre:
Sorry, user pdupre may not run sudo on Teucidide.
Same for sudo -i
Uhm you ARE entering the password for user pdupre, right? Do NOT use
root's password, use you
to run commands directly.
sudo /usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB
[sudo] password for pdupre:
pdupre is not allowed to run sudo on Teucidide. This incident will be reported.
I also tried to put pdupre as member of wheel, but it does not help.
You need to start a new she
On 1/8/19 10:58 AM, Patrick Dupre wrote:
> OK,
>
> Sorry,
>
> But again:
>
> sudo -l
> [sudo] password for pdupre:
> Sorry, user pdupre may not run sudo on Teucidide.
>
>
> Same for sudo -i
Uhm you ARE entering the password for user pdupre, right? Do N
On 08.01.19 19:58, Patrick Dupre wrote:
(Please do not top post)
> sudo -l
> [sudo] password for pdupre:
> Sorry, user pdupre may not run sudo on Teucidide.
I think you have to replace localhost in your sudoers either with your
real hostname or with ALL.
best re
OK,
Sorry,
But again:
sudo -l
[sudo] password for pdupre:
Sorry, user pdupre may not run sudo on Teucidide.
Same for sudo -i
===
Patrick DUPRÉ | | email: pdu...@gmx.com
Laboratoire de
On 08.01.19 19:24, Patrick Dupre wrote:
> sudo -l /usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB/
I guess there was a misunderstanding. 'sudo -l' is a single command to
display the currently allowed rules. So you should try the commands:
sudo -l
sudo /usr/bin/moun
Thank.
Right, but the behavior is exactly the same (with the /)
I need to find the glitch.
And
sudo -l /usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB/
[sudo] password for pdupre:
Sorry, user pdupre may not run sudo on Teucidide.
instead of:
pdupre is not allowed to run sudo on
On 1/8/19 8:38 AM, Ulf Volmer wrote:
> On 08.01.19 10:57, Patrick Dupre wrote:
>
>> With visudo, I did
>> pdupre localhost=/usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB/
>
>> sudo /usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB
>
> When you
On 08.01.19 10:57, Patrick Dupre wrote:
> With visudo, I did
> pdupre localhost=/usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB/
> sudo /usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB
When you allow a specific command for sudo, you *must* use *exactly* the
same command
/dev/mapper/VolGrpUsr_DK0-home /mnt/USB/)
But it does not work
/usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB
mount: only root can do that
or
sudo /usr/bin/mount /dev/mapper/VolGrpUsr_DK0-home /mnt/USB
[sudo] password for pdupre:
pdupre is not allowed to run sudo on Teucidide. This
On 2018-11-08 9:51 p.m., D&R wrote:
> I have tried several ways to connect to remote computer:
>
> $SERVER = qx{ssh -o ConnectTimeout=2 -o ControlPersist=yes $user\@$server
> "sudo hostname| cut -d "." -f1"}; chomp ($SERVER);
>
> but commands that have m
I have tried several ways to connect to remote computer:
$SERVER = qx{ssh -o ConnectTimeout=2 -o ControlPersist=yes $user\@$server
"sudo hostname| cut -d "." -f1"}; chomp ($SERVER);
but commands that have metacharacters, especially the single quote, I can not
get to
On Sat, Apr 28, 2018 at 10:21 AM, D&R wrote:
> On Sat, 28 Apr 2018 06:15:08 -0400 Tom H wrote:
>> On Fri, Apr 27, 2018 at 5:41 PM, Samuel Sieb wrote:
>>> On 04/27/2018 07:26 AM, D&R wrote:
>>>> On Fri, 27 Apr 2018 08:22:12 -0400
>>>> Tom H wrot
D&R wrote:
> On Sat, 28 Apr 2018 06:15:08 -0400
> Tom H wrote:
>
>> On Fri, Apr 27, 2018 at 5:41 PM, Samuel Sieb wrote:
>>> On 04/27/2018 07:26 AM, D&R wrote:
>>>> On Fri, 27 Apr 2018 08:22:12 -0400
>>>> Tom H wrote:
>>
On Sat, 28 Apr 2018 06:15:08 -0400
Tom H wrote:
> On Fri, Apr 27, 2018 at 5:41 PM, Samuel Sieb wrote:
> > On 04/27/2018 07:26 AM, D&R wrote:
> >> On Fri, 27 Apr 2018 08:22:12 -0400
> >> Tom H wrote:
> >>>
> >>> sudo -s
> &
On Fri, Apr 27, 2018 at 5:41 PM, Samuel Sieb wrote:
> On 04/27/2018 07:26 AM, D&R wrote:
>> On Fri, 27 Apr 2018 08:22:12 -0400
>> Tom H wrote:
>>>
>>> sudo -s
>>> sudo su
>>> sudo su -l
>>> sudo sh
>>> sudo sh -l
>>&
1 - 100 of 491 matches
Mail list logo
