8:29 p.m.
Hi All,
Fedora 38
Any way to get this info without being root?
Many thanks,
-T
# nvme smart-log /dev/nvme0n1
Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning : 0
temperature : 34 °C (307 K)
available_spare : 100%
available_spare_threshold : 10%
percentage_used : 2%
endurance group critical warning summary: 0
Data Units Read : 1,163,123,052 (595.52 TB)
Data Units Written : 60,234,320 (30.84 TB)
host_read_commands : 3,597,716,397
host_write_commands : 1,230,457,952
controller_busy_time : 9,407
power_cycles : 2,446
power_on_hours : 5,495
unsafe_shutdowns : 83
media_errors : 0
num_err_log_entries : 3,400
Warning Temperature Time : 0
Critical Composite Temperature Time : 0
Temperature Sensor 1 : 34 °C (307 K)
Temperature Sensor 2 : 41 °C (314 K)
Thermal Management T1 Trans Count : 0
Thermal Management T2 Trans Count : 0
Thermal Management T1 Total Time : 0
Thermal Management T2 Total Time : 0
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
9:36 p.m.
On 10/27/23 18:29, ToddAndMargo via users wrote:
Hi All,
Fedora 38
Any way to get this info without being root?
Many thanks,
-T
# nvme smart-log /dev/nvme0n1
Have a root cron job dump it to a file?
The device node is only accessible to root, so there's no way around that.
You could give your user sudo access for that command. You haven't said
why needing root is a problem.
9:39 p.m.
On 10/27/23 19:36, Samuel Sieb wrote:
On 10/27/23 18:29, ToddAndMargo via users wrote:
> Hi All,
>
> Fedora 38
>
> Any way to get this info without being root?
>
> Many thanks,
> -T
>
>
> # nvme smart-log /dev/nvme0n1
Have a root cron job dump it to a file?
Hmmmmm.
The device node is only accessible to root, so there's no way
around that.
You could give your user sudo access for that command.
Do not like sudo, but I may have to compromise.
You haven't said why needing root is a problem.
Run as a user:
$ nvme smart-log /dev/nvme0n1
/dev/nvme0n1: Permission denied
9:48 p.m.
On 10/27/23 19:39, ToddAndMargo via users wrote:
On 10/27/23 19:36, Samuel Sieb wrote:
> You haven't said why needing root is a problem.
Run as a user:
$ nvme smart-log /dev/nvme0n1
/dev/nvme0n1: Permission denied
Yes, we know that it doesn't work as a user, but you didn't say why you
didn't want to need root to read it.
10:05 p.m.
On 10/27/23 19:48, Samuel Sieb wrote:
On 10/27/23 19:39, ToddAndMargo via users wrote:
> On 10/27/23 19:36, Samuel Sieb wrote:
>> You haven't said why needing root is a problem.
>
> Run as a user:
>
> $ nvme smart-log /dev/nvme0n1
> /dev/nvme0n1: Permission denied
Yes, we know that it doesn't work as a user, but you didn't say why you
didn't want to need root to read it.
As a pop up when I log into Xfce. Just
show the errors
12:23 a.m.
On 10/27/23 20:05, ToddAndMargo via users wrote:
On 10/27/23 19:48, Samuel Sieb wrote:
> On 10/27/23 19:39, ToddAndMargo via users wrote:
>> On 10/27/23 19:36, Samuel Sieb wrote:
>>> You haven't said why needing root is a problem.
>>
>> Run as a user:
>>
>> $ nvme smart-log /dev/nvme0n1
>> /dev/nvme0n1: Permission denied
>
> Yes, we know that it doesn't work as a user, but you didn't say why
> you didn't want to need root to read it.
As a pop up when I log into Xfce. Just
show the errors
Okay I have to manually fire it up, but this is
what I have:
<NVMe.Start.Status.sh>
#! /bin/bash
Drive="/dev/nvme0n1"
echo "$Drive S.M.A.R.T. Status"
echo ""
beesu -c "nvme smart-log $Drive"
echo ""
# read -n 1 -s -p "Press any key to continue..."
/home/linuxutil/Pause.pl
echo ""
</NVMe.Start.Status.sh>
And I launch it with:
$ xterm -fn 8x16 -fg black -bg white -bdc -cc
"33:48,37:48,45-47:48,38:48" -title "NVMe SMART Ststus" -geometry
70x32+340+200 -e /home/linuxutil/NVMe.Smart.Status.sh
8:51 a.m.
On Fri, Oct 27, 2023 at 11:40 PM ToddAndMargo via users <
users(a)lists.fedoraproject.org> wrote:
Do not like sudo, but I may have to compromise.
I don't like sudo either -- it is overkill for many use cases, and the
added complexity means more
potential for security issues.
Have you considered using "doas"?
--
George N. White III
4:58 p.m.
On 10/28/23 06:51, George N. White III wrote:
On Fri, Oct 27, 2023 at 11:40 PM ToddAndMargo via users
<users(a)lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>>
wrote:
Do not like sudo, but I may have to compromise.
I don't like sudo either -- it is overkill for many use cases, and the
added complexity means more
potential for security issues.
Have you considered using "doas"?
Sweet looking command. I just installed it. Thank you!
I have been using "su" and "beesu".
$ doas -u root "nvme smart-log /dev/nvme0n1"
doas: Operation not permitted
5:14 p.m.
On Sat, 2023-10-28 at 14:58 -0700, ToddAndMargo via users wrote:
On 10/28/23 06:51, George N. White III wrote:
> On Fri, Oct 27, 2023 at 11:40 PM ToddAndMargo via users
> <
> users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>
> >
> wrote:
>
> Do not like sudo, but I may have to compromise.
>
>
> I don't like sudo either -- it is overkill for many use cases, and
> the
> added complexity means more
> potential for security issues.
>
> Have you considered using "doas"?
>
Sweet looking command. I just installed it. Thank you!
I have been using "su" and "beesu".
$ doas -u root "nvme smart-log /dev/nvme0n1"
doas: Operation not permitted
Try removing the quotes.
poc
5:56 p.m.
On 10/28/23 15:14, Patrick O'Callaghan wrote:
On Sat, 2023-10-28 at 14:58 -0700, ToddAndMargo via users wrote:
> On 10/28/23 06:51, George N. White III wrote:
>> On Fri, Oct 27, 2023 at 11:40 PM ToddAndMargo via users
>> <
>> users@lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>
>>>
>> wrote:
>>
>> Do not like sudo, but I may have to compromise.
>>
>>
>> I don't like sudo either -- it is overkill for many use cases, and
>> the
>> added complexity means more
>> potential for security issues.
>>
>> Have you considered using "doas"?
>>
>
> Sweet looking command. I just installed it. Thank you!
>
> I have been using "su" and "beesu".
>
> $ doas -u root "nvme smart-log /dev/nvme0n1"
> doas: Operation not permitted
Try removing the quotes.
poc
$ doas -u root nvme smart-log /dev/nvme0n1
doas: Operation not permitted
6:02 a.m.
On Sat, 2023-10-28 at 15:56 -0700, ToddAndMargo via users wrote:
> > $ doas -u root "nvme smart-log /dev/nvme0n1"
> > doas: Operation not permitted
>
> Try removing the quotes.
>
> poc
$ doas -u root nvme smart-log /dev/nvme0n1
doas: Operation not permitted
Does doas ask for your password (you as a user, not root)?
What happens when you use sudo (or 'su -c' - note that in this case
you'll need the quotes)?
What happens if use:
doas nvme ...
i.e. without the '-u root' (since root is the default).
poc
6:06 a.m.
On 10/29/23 04:02, Patrick O'Callaghan wrote:
On Sat, 2023-10-28 at 15:56 -0700, ToddAndMargo via users wrote:
>>> $ doas -u root "nvme smart-log /dev/nvme0n1"
>>> doas: Operation not permitted
>>
>> Try removing the quotes.
>>
>> poc
>
> $ doas -u root nvme smart-log /dev/nvme0n1
> doas: Operation not permitted
Does doas ask for your password (you as a user, not root)?
What happens when you use sudo (or 'su -c' - note that in this case
you'll need the quotes)?
What happens if use:
doas nvme ...
i.e. without the '-u root' (since root is the default).
poc
I am trying to get the information without having
to be root. And it does not have to come from the
nvme command either.
My goal is to do a libnotify popup when I log
into my desktop
6:28 a.m.
On Sun, 2023-10-29 at 04:06 -0700, ToddAndMargo via users wrote:
On 10/29/23 04:02, Patrick O'Callaghan wrote:
> On Sat, 2023-10-28 at 15:56 -0700, ToddAndMargo via users wrote:
> > > > $ doas -u root "nvme smart-log /dev/nvme0n1"
> > > > doas: Operation not permitted
> > >
> > > Try removing the quotes.
> > >
> > > poc
> >
> > $ doas -u root nvme smart-log /dev/nvme0n1
> > doas: Operation not permitted
>
> Does doas ask for your password (you as a user, not root)?
>
> What happens when you use sudo (or 'su -c' - note that in this case
> you'll need the quotes)?
>
> What happens if use:
> doas nvme ...
> i.e. without the '-u root' (since root is the default).
>
> poc
I am trying to get the information without having
to be root. And it does not have to come from the
nvme command either.
My goal is to do a libnotify popup when I log
into my desktop
If the nvme command requires root, it requires root (presumably because
of the direct access to the device).
The point of 'doas' or 'su' or 'sudo' is to get root temporarily
for
the duration of the command. The question here is why is it failing,
and the answer is most likely "because you're doing it wrong". That's
why I'm asking what happens when you run those various alternatives. My
guess is that you have to enable your user via the doas.conf(5) config
file.
I can run doas without issue and have never edited doas.conf. However I
am a member the 'wheel' group, which the default doas.conf does enable:
$ cat /etc/doas.conf
# Allow wheel by default
permit :wheel
So I suggest you try as a member of the wheel group and see what
happens.
poc
6 a.m.
On Sat, Oct 28, 2023 at 6:59 PM ToddAndMargo via users <
users(a)lists.fedoraproject.org> wrote:
$ doas -u root "nvme smart-log /dev/nvme0n1"
doas: Operation not permitted
I use:
% doas nvme smart-log /dev/nvme0n1
doas (<user>@<host>) password:
Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning : 0
temperature : 29 °C (302 K)
[...]
Thermal Management T2 Total Time : 0
--
George N. White III
6:04 a.m.
On 10/29/23 04:00, George N. White III wrote:
On Sat, Oct 28, 2023 at 6:59 PM ToddAndMargo via users
<users(a)lists.fedoraproject.org <mailto:users@lists.fedoraproject.org>>
wrote:
$ doas -u root "nvme smart-log /dev/nvme0n1"
doas: Operation not permitted
I use:
% doas nvme smart-log /dev/nvme0n1
doas (<user>@<host>) password:
Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
critical_warning : 0
temperature : 29 °C (302 K)
[...]
Thermal Management T2 Total Time : 0
--
George N. White III
I am trying to get around the password issue so I
can just do a libnotify popup when I log into my
desktop
7:19 a.m.
On Sun, 2023-10-29 at 04:04 -0700, ToddAndMargo via users wrote:
I am trying to get around the password issue so I
can just do a libnotify popup when I log into my
desktop
I recall there's sudo configuration options for users and/or particular
commands that don't require a password.
"To run particular commands without sudo password in Linux, you can use
the NOPASSWD directive in the /etc/sudoers file. This directive allows
you to specify a list of commands that can be run without requiring a
password."
Of course there are risks involved, you'll have decide about that for
yourself.
--
NB: All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the list.
The following system info data is generated fresh for each post:
uname -rsvp
Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53
UTC 2023 x86_64
8:48 p.m.
On 10/29/23 05:19, Tim via users wrote:
On Sun, 2023-10-29 at 04:04 -0700, ToddAndMargo via users wrote:
> I am trying to get around the password issue so I
> can just do a libnotify popup when I log into my
> desktop
I recall there's sudo configuration options for users and/or particular
commands that don't require a password.
"To run particular commands without sudo password in Linux, you can use
the NOPASSWD directive in the /etc/sudoers file. This directive allows
you to specify a list of commands that can be run without requiring a
password."
Of course there are risks involved, you'll have decide about that for
yourself.
Seems like I am going to have to compromise on sudo
11:06 p.m.
On Sun, Oct 29, 2023 at 9:49 PM ToddAndMargo via users
<users(a)lists.fedoraproject.org> wrote:
On 10/29/23 05:19, Tim via users wrote:
> On Sun, 2023-10-29 at 04:04 -0700, ToddAndMargo via users wrote:
>> I am trying to get around the password issue so I
>> can just do a libnotify popup when I log into my
>> desktop
>
> I recall there's sudo configuration options for users and/or particular
> commands that don't require a password.
>
> "To run particular commands without sudo password in Linux, you can use
> the NOPASSWD directive in the /etc/sudoers file. This directive allows
> you to specify a list of commands that can be run without requiring a
> password."
>
> Of course there are risks involved, you'll have decide about that for
> yourself.
Seems like I am going to have to compromise on sudo
I believe you can avoid that if you want. Write a C program that calls
fork/exec. Call nvme in the fork. Set the setuid bit on the program.
You can't do it in a wrapper script because you can't setuid on scripts.
Jeff
3:41 a.m.
On Mon, Oct 30, 2023 at 4:36 AM Roberto Ragusa <mail(a)robertoragusa.it> wrote:
On 10/30/23 05:06, Jeffrey Walton wrote:
> You can't do it in a wrapper script because you can't setuid on scripts.
But you can enable sudo for a single script.
(this was the intended way to use sudo, as far as I know)
I may be crossing wires, but I thought OP already ruined out sudo,
doas and friends.
Jeff
5:09 a.m.
On 10/30/23 01:41, Jeffrey Walton wrote:
On Mon, Oct 30, 2023 at 4:36 AM Roberto Ragusa
<mail(a)robertoragusa.it> wrote:
>
> On 10/30/23 05:06, Jeffrey Walton wrote:
>
>> You can't do it in a wrapper script because you can't setuid on scripts.
> But you can enable sudo for a single script.
> (this was the intended way to use sudo, as far as I know)
I may be crossing wires, but I thought OP already ruined out sudo,
doas and friends.
Jeff
I do not want to have to enter root's password to get
the information.
I looks like I am going to have to hold my nose
and use sudo
5:34 a.m.
On Mon, 2023-10-30 at 03:09 -0700, ToddAndMargo via users wrote:
On 10/30/23 01:41, Jeffrey Walton wrote:
> On Mon, Oct 30, 2023 at 4:36 AM Roberto Ragusa
> <mail(a)robertoragusa.it> wrote:
> >
> > On 10/30/23 05:06, Jeffrey Walton wrote:
> >
> > > You can't do it in a wrapper script because you can't setuid on
> > > scripts.
> > But you can enable sudo for a single script.
> > (this was the intended way to use sudo, as far as I know)
>
> I may be crossing wires, but I thought OP already ruined out sudo,
> doas and friends.
>
> Jeff
I do not want to have to enter root's password to get
the information.
I looks like I am going to have to hold my nose
and use sudo
This is exactly what sudo is for. Not sure why you're trying to avoid
it.
poc
5:38 a.m.
On Mon, 2023-10-30 at 00:06 -0400, Jeffrey Walton wrote:
On Sun, Oct 29, 2023 at 9:49 PM ToddAndMargo via users
<users(a)lists.fedoraproject.org> wrote:
>
> On 10/29/23 05:19, Tim via users wrote:
> > On Sun, 2023-10-29 at 04:04 -0700, ToddAndMargo via users wrote:
> > > I am trying to get around the password issue so I
> > > can just do a libnotify popup when I log into my
> > > desktop
> >
> > I recall there's sudo configuration options for users and/or
> > particular
> > commands that don't require a password.
> >
> > "To run particular commands without sudo password in Linux, you
> > can use
> > the NOPASSWD directive in the /etc/sudoers file. This directive
> > allows
> > you to specify a list of commands that can be run without
> > requiring a
> > password."
> >
> > Of course there are risks involved, you'll have decide about that
> > for
> > yourself.
>
> Seems like I am going to have to compromise on sudo
I believe you can avoid that if you want. Write a C program that
calls
fork/exec. Call nvme in the fork. Set the setuid bit on the program.
Yes, and open yourself to potential security holes unless you know
exactly what you're doing (including setting the proper security
context). Problems with setuid programs written without due care and
attention are a classic entry point for attack.
Sudo exists to avoid the necessity of this sort of thing.
poc
8:12 p.m.
On 10/30/23 03:38, Patrick O'Callaghan wrote:
On Mon, 2023-10-30 at 00:06 -0400, Jeffrey Walton wrote:
> On Sun, Oct 29, 2023 at 9:49 PM ToddAndMargo via users
> <users(a)lists.fedoraproject.org> wrote:
>>
>> On 10/29/23 05:19, Tim via users wrote:
>>> On Sun, 2023-10-29 at 04:04 -0700, ToddAndMargo via users wrote:
>>>> I am trying to get around the password issue so I
>>>> can just do a libnotify popup when I log into my
>>>> desktop
>>>
>>> I recall there's sudo configuration options for users and/or
>>> particular
>>> commands that don't require a password.
>>>
>>> "To run particular commands without sudo password in Linux, you
>>> can use
>>> the NOPASSWD directive in the /etc/sudoers file. This directive
>>> allows
>>> you to specify a list of commands that can be run without
>>> requiring a
>>> password."
>>>
>>> Of course there are risks involved, you'll have decide about that
>>> for
>>> yourself.
>>
>> Seems like I am going to have to compromise on sudo
>
> I believe you can avoid that if you want. Write a C program that
> calls
> fork/exec. Call nvme in the fork. Set the setuid bit on the program.
Yes, and open yourself to potential security holes unless you know
exactly what you're doing (including setting the proper security
context). Problems with setuid programs written without due care and
attention are a classic entry point for attack.
Sudo exists to avoid the necessity of this sort of thing.
poc
I finally broke down and used sudo (I despise the fussing
required and the half way documentation)
https://imgur.com/uH74gnT.png
7:33 p.m.
On Mon, Oct 30, 2023 at 10:13 PM ToddAndMargo via users <
users(a)lists.fedoraproject.org> wrote:
On 10/30/23 03:38, Patrick O'Callaghan wrote:
> On Mon, 2023-10-30 at 00:06 -0400, Jeffrey Walton wrote:
>> On Sun, Oct 29, 2023 at 9:49 PM ToddAndMargo via users
>> <users(a)lists.fedoraproject.org> wrote:
>>>
>>> On 10/29/23 05:19, Tim via users wrote:
>>>> On Sun, 2023-10-29 at 04:04 -0700, ToddAndMargo via users wrote:
>>>>> I am trying to get around the password issue so I
>>>>> can just do a libnotify popup when I log into my
>>>>> desktop
>>>>
>>>> I recall there's sudo configuration options for users and/or
>>>> particular
>>>> commands that don't require a password.
>>>>
>>>> "To run particular commands without sudo password in Linux, you
>>>> can use
>>>> the NOPASSWD directive in the /etc/sudoers file. This directive
>>>> allows
>>>> you to specify a list of commands that can be run without
>>>> requiring a
>>>> password."
>>>>
>>>> Of course there are risks involved, you'll have decide about that
>>>> for
>>>> yourself.
>>>
>>> Seems like I am going to have to compromise on sudo
Why? Doas also has settings to allow specific users to run a specific
command without password.
>>
>> I believe you can avoid that if you want. Write a C program that
>> calls
>> fork/exec. Call nvme in the fork. Set the setuid bit on the program.
>
> Yes, and open yourself to potential security holes unless you know
> exactly what you're doing (including setting the proper security
> context). Problems with setuid programs written without due care and
> attention are a classic entry point for attack.
>
> Sudo exists to avoid the necessity of this sort of thing.
>
> poc
I finally broke down and used sudo (I despise the fussing
required and the half way documentation)
https://imgur.com/uH74gnT.png
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
7:52 p.m.
On 10/31/23 17:33, George N. White III wrote:
On Mon, Oct 30, 2023 at 10:13 PM ToddAndMargo via users
Why? Doas also has settings to allow specific users to run a
specific
command without password.
No particular reason. I had to choose one or the other.
Doas look sweet. I copied it down into my keepers file
for future use.
189
days inactive
193
days old
26 comments
7 participants
participants (7)
-
George N. White III -
Jeffrey Walton -
Patrick O'Callaghan -
Roberto Ragusa -
Samuel Sieb -
Tim -
ToddAndMargo