On 4/1/24 02:32, François Patte wrote:
Le 2024-04-01 10:40, Samuel Sieb a écrit :
On 4/1/24 01:08, François Patte wrote:
Up to yesterday, I was allowed to shutdown and hibernate my machine
as a simple user.
Using the gui or the command line?
I use xfce and in the panel there is tab with
On Mon, 2024-04-01 at 11:32 +0200, François Patte wrote:
> Le 2024-04-01 10:40, Samuel Sieb a écrit :
> > On 4/1/24 01:08, François Patte wrote:
> > > Up to yesterday, I was allowed to shutdown and hibernate my
> > > machine as
> > > a simple user.
> &
Le 2024-04-01 10:40, Samuel Sieb a écrit :
On 4/1/24 01:08, François Patte wrote:
Up to yesterday, I was allowed to shutdown and hibernate my machine as
a simple user.
Using the gui or the command line?
I use xfce and in the panel there is tab with the user name, using this
you can
On 4/1/24 01:08, François Patte wrote:
Up to yesterday, I was allowed to shutdown and hibernate my machine as a
simple user.
Using the gui or the command line?
Yesterday a powercut while the machine was up suppressed this
feature I don't understand why.
How can recover this fe
Bonjour,
Up to yesterday, I was allowed to shutdown and hibernate my machine as a
simple user.
Yesterday a powercut while the machine was up suppressed this
feature I don't understand why.
How can recover this feature?
Thank you
--
François Patte
UFR de mathématiques et informa
On 7/26/23 6:42 AM, stan via users wrote:
[... snip ...]
I have plymouth installed, and see messages at both start and exit on
f37. I think the key thing to get that behavior with plymouth
installed is to remove the rhgb and quiet from the kernel command line.
Try it first, by hitting a key du
On 7/25/23 11:09 AM, home user wrote:
Good morning,
I want to see console logging during shutdown automatically, by default.
How do I do that?
thanks,
Bill.
(responding to posts about plymouth)
What's making me uncomfortable is the huge number of files (NOT in /home) that contain the s
ot;; I was overwhelmed. I tried finding files and directories (not in user directory trees) whose name contained "plymouth"; I was overwhelmed. I gather plymouth is used for much more than logging during boot-up and shutdown.
Strange. When I searched on "plymouth linux" the
files and directories
(not in user directory trees) whose name contained "plymouth"; I was
overwhelmed. I gather plymouth is used for much more than logging
during boot-up and shutdown.
Strange. When I searched on "plymouth linux" the first two hits I got
were the Arch L
> On 26 Jul 2023, at 02:43, home user wrote:
> I tried to research plymouth. I found little information about it; no hint
> of any configuration or customization file.
Its only config is the theme to use as I recall.
I wrote one of those theme for an embedded system a long time ago.
>
> So
On Tue, 25 Jul 2023 19:43:13 -0600
home user wrote:
> On 7/25/23 2:42 PM, Barry Scott wrote:
>
> >
> > I uninstall plymouth so that there is no splash screen on many of
> > my systems so that I can see the console messages.
> >
> > Without plymouth sys
On Tue, 2023-07-25 at 19:49 -0600, home user wrote:
> On 7/25/23 3:08 PM, Patrick O'Callaghan wrote:
>
> > Note that you can see the console output during startup by pressing
> > Esc
> > after the flashscreen shows. I don't know if there's a way to get
>
On 7/25/23 18:43, home user wrote:
On 7/25/23 2:42 PM, Barry Scott wrote:
I uninstall plymouth so that there is no splash screen on many of my
systems so
that I can see the console messages.
Without plymouth systemd will show start up and shutdown messages on
the console.
I checked; dnf
home user composed on 2023-07-25 19:43 (UTC-0600):
> I'm very nervous about removing plymouth. Is there a way of controlling
> shutdown (and boot-up) logging via configuration files? I would think that
> would be much easier and safer.
IMO, the primary purpose of Plymouth is
On 7/25/23 3:08 PM, Patrick O'Callaghan wrote:
Note that you can see the console output during startup by pressing Esc
after the flashscreen shows. I don't know if there's a way to get it
during shutdown.
That works (much of the time) during shutdown, too. But often it takes a
On 7/25/23 2:42 PM, Barry Scott wrote:
I uninstall plymouth so that there is no splash screen on many of my systems so
that I can see the console messages.
Without plymouth systemd will show start up and shutdown messages on the
console.
I checked; dnf confirms I have plymouth.
I tried to
On Tue, 2023-07-25 at 21:42 +0100, Barry Scott wrote:
>
>
> > On 25 Jul 2023, at 18:09, home user wrote:
> >
> > Good morning,
> >
> > I want to see console logging during shutdown automatically, by
> > default.
> > How do I do that?
>
>
> On 25 Jul 2023, at 18:09, home user wrote:
>
> Good morning,
>
> I want to see console logging during shutdown automatically, by default.
> How do I do that?
I uninstall plymouth so that there is no splash screen on many of my systems so
that I can see the console
Good morning,
I want to see console logging during shutdown automatically, by default.
How do I do that?
thanks,
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora
Now that terminal emulator sessions are no longer treated as separate logins, commands like
"shutdown" and Network UPS Tools that try to use "wall" to alert users to
impending doom are effectively muted.
This should probably be reported as a bug in the "shutdown&
On Thu, 2023-02-16 at 09:36 +1030, Tim via users wrote:
> Many BIOSs will also let you set a wake up time within them. It *may*
> also be possible for that time to be set from the OS (such as if you
> wanted to change it).
>
> Remember that the hardware clock may be different from the system
> cl
ontrol.
> It has to be automatic (of course I could say restart at 12:00,
> but I have to say it at the shutdown)
Many BIOSs will also let you set a wake up time within them. It *may*
also be possible for that time to be set from the OS (such as if you
wanted to change it).
Remember that the
On Wed, 15 Feb 2023 23:38:34 +0100
Patrick Dupre wrote:
> But does it means that it will boot when the power will be back?
That's how it works on my systems (where it functions correctly - not
all motherboards get it right). Sometimes this surprises me if
I'm working on a system and plug it in, f
>
> > Actually, this will be done more or less automatically if I do not
> > do anything, except that the shutdown will be hard when the power
> > will be turned off.
>
> A lot of BIOS have settings for things like "boot at power on".
> You could shut do
On Wed, 15 Feb 2023 23:16:05 +0100
Patrick Dupre wrote:
> Actually, this will be done more or less automatically if I do not
> do anything, except that the shutdown will be hard when the power
> will be turned off.
A lot of BIOS have settings for things like "boot at power on&qu
Hello,
I would like to set one of the following
1) shutdown now and restart at a given time,
2) shutdown (halt) and restart automatically when the next power
with be back on (of course at the shutdown, the power will be on,
it will be turned off for a couple of hours, and it will be
backed
Two years later, I can say that this error might still be a thing.
I concluded that the most likely cause is my mother. Jokes aside, she unplugged
the power chord before the pc switches off completely. Through the years, she
managed to crash in the same way f33, f34, and now f35.
This time I had
temd-cryptsetup@luks\x2d23.service stop running
>
>
> Home and other make sense given your earlier comment, but what are the
> other two? Do the number of entries in /etc/crypttab match the number
> of LUKS partitions? (What's in /proc/mounts during the failed shutdown?)
Wh
service stop running
> > 6047 systemd-cryptsetup@luks\x2d23.service stop running
>
>
> Home and other make sense given your earlier comment, but what are the
> other two? Do the number of entries in /etc/crypttab match the number
> of LUKS partitions? (What's in /proc
other make sense given your earlier comment, but what are the
other two? Do the number of entries in /etc/crypttab match the number
of LUKS partitions? (What's in /proc/mounts during the failed shutdown?)
___
users mailing list --
On Thu, Dec 2, 2021 at 2:06 PM Gordon Messmer
wrote:
> On 12/1/21 18:03, murph nj wrote:
> >
> > lsof showed nothing that I could see.
>
>
> Nothing, or nothing interesting? I'd expect you to at least see the CWD
> of the debug shell.
>
>
Got another opportunity, redirected lsof /home and lsof /
The contents of /proc/mounts might be interesting. I'd run
> "lsof /path" where path is the longest mount point path of the volumes
> still listed in /proc/mounts.
>
>
I'll give it a shot next time it hangs up on shutdown. Any ideas on how to
make the er
On 12/1/21 18:03, murph nj wrote:
lsof showed nothing that I could see.
Nothing, or nothing interesting? I'd expect you to at least see the CWD
of the debug shell.
The stop job rotates between four mounted volumes, and the
lvm2-monitor.service.
In the past, I've seen lvm2-monitor beh
On Wed, 1 Dec 2021 21:03:16 -0500
murph nj wrote:
> So, as far as dragging people through debugging seems somewhat futile
> to me, unless collectively you think that it is worthwhile to pursue
> this. I'm game if this can help the Fedora community, but the system
> is working, I can back up, and
the jobs and then do a systemctl status on each
> one of them to find out what they are up to.
>
>
> Well, I finally enabled the shell, and it (as it is intermittent) hung up
on shutdown.
lsof showed nothing that I could see.
The stop job rotates between four mounted volumes, an
On Thu, Sep 30, 2021 at 4:13 PM Gordon Messmer wrote:
>
> On 9/30/21 12:41, Chris Murphy wrote:
> > Seems likely to me some service is not quitting properly, preventing /
> > from being unmounted
>
>
> If that were the case, there might be information about an exit failure
> in the log. On the ne
On 9/30/21 12:41, Chris Murphy wrote:
Seems likely to me some service is not quitting properly, preventing /
from being unmounted
If that were the case, there might be information about an exit failure
in the log. On the next boot, "journalctl -b -1" might have useful info.
I also wonder i
here
> in the current version as well.
>
> Somewhere around 1 out of every 10 shutdowns, the system goes down to
> "[ OK ] Reached target System Shutdown", but then,
> "[ *** ] a stop job is running for Cryptography setup for luks- LUKS volumes>"
>
> It
On Wed, 29 Sep 2021 14:17:01 -0400
murph nj wrote:
> I'm having an issue shutting down.
[snip]
> I haven't found anything interesting in /var/log/messages regarding
> it.
>
> Any suggestions to further troubleshooting?
I think this is an artifact of the shutdown pr
On 9/29/21 14:17, Samuel Sieb wrote:
Somehow you sent this as a reply to another thread that most people will
probably ignore. I suggest sending it again as not a reply.
And immediately after sending that I saw that there were more emails in
my inbox and you had already done that. Sorry!
__
Somehow you sent this as a reply to another thread that most people will
probably ignore. I suggest sending it again as not a reply.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject
f every 10 shutdowns, the system goes down to
"[ OK ] Reached target System Shutdown", but then,
"[ *** ] a stop job is running for Cryptography setup for luks-"
It typically goes for about 1/2 hour if I don't get fed up, and hold the
power button down.
I just saw after that
I'm having an issue shutting down. Fedora 34, just updated to 35, same
problem. (It was around in 33 as well, I've been putting up with it.)
Somewhere around 1 out of 10 shutdowns, the system goes down to "[ OK ]
Reached target System Shutdown", but then,
[ *** ] a sto
On 04/28/2020 10:28 AM, Digimer wrote:
Auto-installing updates on shutdown is a terrible idea and should NOT be
the default behaviour of any modern OS.
And, of course, if somebody had the temerity to open a BZ on this
behavior, it would be instantly closed as NOTABUG
On 2020-04-28 11:57 a.m., Jonathan Billings wrote:
> On Tue, Apr 28, 2020 at 10:54:15AM -0400, Tom Horsley wrote:
>>
>> I try to shutdown my new fedora 32 virtual machine.
>> It immediately says:
>>
>> "Installing updates, do not turn off"
>>
>&
On 2020-04-23 06:57, Ed Greshko wrote:
There have been updates to the kernel since that time.
Every day. I keep hoping a kernel update will come through
and fix it
You're on 5.5.17-200 now?
$ uname -r
5.5.17-200.fc31.x86_64
___
users mailing list -
aid, this is probably a resource issue. Something is hogging
the CPU or memory, and limiting the time slice for your typing
interrupts. The keystroke logger on your system is misbehaving. Or
maybe it is the bitcoin miner causing the problem. We'll
send out new ones as soon as possible. ;-)
>
>>> And to just be clear, if no slow down is apparent, shutdown
>>> and reboot work perfectly: they do not hang
>>
>> So, you're saying that if you see a slowdown then you'll have the issue with
>> reboot/shutdown.
>
> Yes. And time does not heal.
correlate to certain web pages, and its timing seems
> to be rather random and often it seems to happen unattended. On the
> 32gb laptop when it gets slow enough that I notice I find what is
> using all of the ram and kill it and that clears up the issue.
> Excessive swap usage will cause sh
On Thu, 2020-04-23 at 06:03 -0700, ToddAndMargo via users wrote:
> > It sounds as if this issue happens for you frequently? And, are you still
> > on the kernel shown in the
> > BZ?
>
> What is BZ?
Bugzilla, the Fedora bug reporting system.
poc
___
On 2020-04-23 05:25, Ed Greshko wrote:
On 2020-04-23 20:06, ToddAndMargo via users wrote:
On 2020-04-23 03:53, ToddAndMargo via users wrote:
Fedora 31, x64
Xfce 4.14
Shutdown hangs:
https://bugzilla.redhat.com/show_bug.cgi?id=1815686
Hi All,
Randomly and not associated with any particular
real task hung bugs shutdown won't ever finish
and you will have to force it off as the messages is reporting it hung
for XX seconds, but really it will never get out the the deadlock, or
whatever needs to do will never complete.
On my laptop (32gb) I only get a tiny bit slow when firefo
On 2020-04-23 20:06, ToddAndMargo via users wrote:
> On 2020-04-23 03:53, ToddAndMargo via users wrote:
>> Fedora 31, x64
>> Xfce 4.14
>>
>> Shutdown hangs:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1815686
>>
>> Hi All,
>>
>> Rando
On 2020-04-23 03:53, ToddAndMargo via users wrote:
Fedora 31, x64
Xfce 4.14
Shutdown hangs:
https://bugzilla.redhat.com/show_bug.cgi?id=1815686
Hi All,
Randomly and not associated with any particular program,
my system will slow down. It becomes obvious when I can
type faster than letters
Fedora 31, x64
Xfce 4.14
Shutdown hangs:
https://bugzilla.redhat.com/show_bug.cgi?id=1815686
Hi All,
Randomly and not associated with any particular program,
my system will slow down. It becomes obvious when I can
type faster than letters appear. And when this happens,
a reboot will fix it
Hi All,
Fedora 31
Shutdown hangs:
https://bugzilla.redhat.com/show_bug.cgi?id=1815686
Anyone else having problems with shutdown? It
gets to the point where it says
Target reached: reboot / power off
it hands for about a minutes. Then it constantly
repeats the values in my CPU registers
Hi folks,
when I shutdown my Fedora 31 XFCE via the menu, the system goes down,
and then after one or two seconds automatically restarts.
What I' ve to do as a work-around to shut the system down is to log into
a console and type "sudo halt" which halts the system. When a mes
On Mon, 25 Nov 2019 15:13:01 -0700
S.Bob wrote:
> Any thoughts on how to debug this?
I don't know about debug, but it looks like the nouveau driver
is crashing, so you could try installing the nvidia driver
from rpmfusion and see if it gets better.
___
Hi all;
I've just installed Fedora 31, on a thinkpad P51s
Every time I shutdown it hangs with the following text and never powers off.
Any thoughts on how to debug this?
Thanks in advance.
Nov 25 08:07:21 F31host kernel: [ cut here ]
Nov 25 08:07:21 F3
ailing, but you don't really know what the underlying
> cause is for it to fail.
>
> What exactly was the "improper shutdown"
>
> The easiest way to debug is to livecd boot it mount up the old
> filessystems on say /oldroot (rootfs) mount /oldroot/usr for usr and
>
ailing, but you don't really know what the underlying
> cause is for it to fail.
>
> What exactly was the "improper shutdown"
A failing battery (I think) caused it to shut down when I wasn't
ready, and didn't shut down properly. Then I accidentally opened the
lid,
l.
What exactly was the "improper shutdown"
The easiest way to debug is to livecd boot it mount up the old
filessystems on say /oldroot (rootfs) mount /oldroot/usr for usr and
so forth and then cd /oldroot and do a "chroot ."
I would expect the chroot . to fail with some sort of
On Mon, Sep 9, 2019 at 9:07 PM Tony Nelson wrote:
>
> Usually, when it all goes wrong just after pivot-root, there is a
> problem with the new (real) root. Exactly how it goes wrong is not
> useful. I would look hard at whatever is mounted at /sysroot. It
> should be what you expect / (root) to
On 19-09-09 14:10:24, murph nj wrote:
Tony:
Can you give me some insight as to what the boot process does next
AFTER that pivot point? The output I'm getting isn't enlightening me,
and I'm not quite sure where to look next.
...
Usually, when it all goes wrong just after pivot-root, there is
Tony:
Can you give me some insight as to what the boot process does next
AFTER that pivot point? The output I'm getting isn't enlightening me,
and I'm not quite sure where to look next.
I can just reinstall, but I'm trying to learn more about how to
recover from errors, instead of taking the eas
On Thu, Sep 5, 2019 at 11:08 AM sixpack13 wrote:
>
> e2fsck is for ext -partitions
> AFAIK /boot/efi is fat !
You are correct. I already checked, all the partitions are fine.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
e2fsck is for ext -partitions
AFAIK /boot/efi is fat !
___
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-o
On Wed, 4 Sep 2019 17:42:40 -0400
murph nj wrote:
> I had not, but I edited from the grub menu, and eliminated them. I
> was then able to see the messages. (I was able to see them previously
> by hitting the escape key right after entering my password for the
> disks.)
>
> Everything left on th
On Wed, Sep 4, 2019 at 9:56 PM Tony Nelson wrote:
>
>
> It dies trying to pivot-root, so add to the kernel command line
>
> rd.break=pre-pivot
>
Interesting. I was able to drop to a shell. I took a look at the
journal, and it looked like a possible hibernation problem, so I took
that out
On 19-09-04 17:42:40, murph nj wrote:
...
Everything left on the screen after the kernel panic is (too much to
type)
https://imgur.com/a/kf81crl
...
Unfortunately, it goes right to a kernel panic, so no prompts at all
to work with. (I'd have chewed on it more before asking for help if I
h
On Wed, Sep 4, 2019 at 5:42 PM murph nj wrote:
>
> On Wed, Sep 4, 2019 at 4:21 PM stan via users
> wrote:
> >
> > On Wed, 4 Sep 2019 15:05:36 -0400
> > murph nj wrote:
> >
> > > I was able to mount the drives, and check them, no problems.
> >
> > Did that include the boot partition, where the ke
On Wed, Sep 4, 2019 at 4:21 PM stan via users
wrote:
>
> On Wed, 4 Sep 2019 15:05:36 -0400
> murph nj wrote:
>
> > I was able to mount the drives, and check them, no problems.
>
> Did that include the boot partition, where the kernels and initramfs'
> are?
>
I had not, but on your suggestion, I
On Wed, 4 Sep 2019 15:05:36 -0400
murph nj wrote:
> I was able to mount the drives, and check them, no problems. I was
> also able to move all of my important data off of the drives to an
> external, so I'm not worried about any loss to the data on the drives.
> No worries of fatal mistakes anym
I was able to mount the drives, and check them, no problems. I was
also able to move all of my important data off of the drives to an
external, so I'm not worried about any loss to the data on the drives.
No worries of fatal mistakes anymore.
I also took a look at the journals that were left, the
On Wed, 4 Sep 2019 12:33:59 -0400
murph nj wrote:
> The power supply was not the problem, it was the battery. All
> subsequent testing has been done plugged into power. It also boots
> just fine from a USB stick with either Mint or Fedora.
>
> There are three kernels available from the boot me
On Wed, Sep 4, 2019 at 11:45 AM stan via users
wrote:
>
>
> The switch root is changing from the initramfs to the installed OS. If
> there is a power problem, it is possible that memory is not working
> properly, and disk reads are erronious. Fix the power supply before
> you go any further. An
On Tue, 3 Sep 2019 22:31:52 -0400
murph nj wrote:
> I've got an Acer laptop that has been shutting down suddenly. (I
> suspect a bad battery, working on that.)
>
> After a sudden shutdown last night, I now get a kernel panic on boot
> right after "Starting Switch Roo
Hi all:
I've got an odd problem that I was hoping for some help on.
The laptop was previously working fine, I am running F30, updated regularly.
I've got an Acer laptop that has been shutting down suddenly. (I
suspect a bad battery, working on that.)
After a sudden shutdown last ni
On 19-04-08 08:45:37, Sam Varshavchik wrote:
According to /var/log/messages, systemd thinks the system is going
down for a shutdown or reboot:
...
What in blazes is it doing?
cron jobs.
--
TonyN
According to /var/log/messages, systemd thinks the system is going down for
a shutdown or reboot:
Apr 8 08:38:12 monster systemd[52873]: Stopped target Default.
Apr 8 08:38:12 monster systemd[52873]: Stopped target Basic System.
Apr 8 08:38:12 monster systemd[52873]: Stopped target Sockets
DIA Quadro P500 2GB GDDR5
Ever since then I've had issues with lockups, cpu 'stuck' at 100%,
shutdown hangs, etc
I upgraded to Fedora29 and most of the lockup and cpu stuck issues went
away but the shutdown hang issue remained.
Often I would see /var/log/messages entries like this:
I've been seeing this for a long time but it hasn't seemed to cause any
issues so I've left it alone.
Per this link:
https://unix.stackexchange.com/questions/378678/why-do-i-get-the-error-failed-unmounting-var-during-shutdown
It has to do with having a separate /var (common) and
On 9/28/18 4:08 AM, Neal Becker wrote:
> Matthew Miller wrote:
>
>> You're not using spot pricing, are you?
>>
> No.
>
> I'm becoming more convinced that machines get shutdown when load average >
> #cores for too long, but it seems rather randomly. Th
Matthew Miller wrote:
> You're not using spot pricing, are you?
>
No.
I'm becoming more convinced that machines get shutdown when load average >
#cores for too long, but it seems rather randomly. The reason I'm asking
here is just in case that is part of fedora cloud
You're not using spot pricing, are you?
On Tue, Sep 25, 2018 at 03:32:49PM -0400, Neal Becker wrote:
> I'm using f28 cloud on AWS as a compute farm. It seems that instances
> randomly shutdown within hours of starting. An example log:
>
> ...
> Fedora 28 (Cloud Edi
On 9/26/18 5:03 AM, Neal Becker wrote:
> Rick Stevens wrote:
>
>> On 9/25/18 12:32 PM, Neal Becker wrote:
>>> I'm using f28 cloud on AWS as a compute farm. It seems that instances
>>> randomly shutdown within hours of starting. An example log:
>&
Rick Stevens wrote:
> On 9/25/18 12:32 PM, Neal Becker wrote:
>> I'm using f28 cloud on AWS as a compute farm. It seems that instances
>> randomly shutdown within hours of starting. An example log:
>>
>> ...
>> Fedora 28 (Cloud Edition)
>> Kerne
On 9/25/18 12:32 PM, Neal Becker wrote:
> I'm using f28 cloud on AWS as a compute farm. It seems that instances
> randomly shutdown within hours of starting. An example log:
>
> ...
> Fedora 28 (Cloud Edition)
> Kernel 4.16.3-301.fc28.x86_64 on an x86_64 (ttyS0)
>
&
I'm using f28 cloud on AWS as a compute farm. It seems that instances
randomly shutdown within hours of starting. An example log:
...
Fedora 28 (Cloud Edition)
Kernel 4.16.3-301.fc28.x86_64 on an x86_64 (ttyS0)
Stopping Restore /run/initramfs on shutdown...
[[0;32m OK
On 9/19/18 1:24 PM, Louis Garcia wrote:
Is there a way to have fedora workstation to update on shutdown? When
a user logs off or shutdown there box I would like fedora to pkcon
update -y or dnf upgrade -y. I thought about creating a systemd unit
file to do this but would that conflict with
On Wed, 2018-09-19 at 23:18 +, Rick Stevens wrote:
> 95% of the time "dnf --refresh -y upgrade" won't cause issues, but
> it's that 5% of the time where it DOES screw up that will drive you
> barking mad. Microsoft has had some absolutely horrific problems
>
On 9/20/18 8:09 AM, Rick Stevens wrote:
> Do what you wish, just be bloody careful about it. That's all I'm
> saying.
Just a FWIW.
It has been my experience that those responsible for 100s+ system mostly do
their due
diligence when it comes to configuring automatic updates.
And those that didn'
That is what I do. I have a local repo that I sync. Workstations only have
the local repo enabled. After I'm satisfied the updates cause no pain I let
the rest update. Now my users never bother to update so I end up going
around when their are other issues
and update as I go. I just wanted to know
On 9/19/18 4:45 PM, Louis Garcia wrote:
> I handle hundreds of workstations, I am not about to manually update
> everyone. dnf-automatic the best choice right now.
Go right ahead. I'm just warning you.
I managed 1500-3000 systems in multiple datacenters world wide and at
least that many additiona
x27;s
> that 5% of the time where it DOES screw up that will drive you barking
> mad. Microsoft has had some absolutely horrific problems doing this
> "upgrade on shutdown" behind the scenes crud and THEY have utter control
> of ALL the software being upgraded during the process. T
of the time "dnf --refresh -y upgrade" won't cause issues, but it's
that 5% of the time where it DOES screw up that will drive you barking
mad. Microsoft has had some absolutely horrific problems doing this
"upgrade on shutdown" behind the scenes crud and THEY have ut
How well does dnf-automatic work? I often rebuild workstations through pxe
and kickstart so a bad update is not an issue.
On Wed, Sep 19, 2018 at 2:36 PM fred roller wrote:
> I whole hardheartedly agree with Rick on this point. That being said,
> yes, put the script in the shutdown se
I whole hardheartedly agree with Rick on this point. That being said, yes,
put the script in the shutdown sequence. Inject it either first or where
ever makes the most since. It has been awhile since I messed with this but
I think you need to research manipulation of the rc.local directory files
On 9/19/18 10:24 AM, Louis Garcia wrote:
> Is there a way to have fedora workstation to update on shutdown? When a
> user logs off or shutdown there box I would like fedora to pkcon update
> -y or dnf upgrade -y. I thought about creating a systemd unit file to do
> this but would t
Is there a way to have fedora workstation to update on shutdown? When a
user logs off or shutdown there box I would like fedora to pkcon update -y
or dnf upgrade -y. I thought about creating a systemd unit file to do this
but would that conflict with offline update?
--Thanks
1 - 100 of 583 matches
Mail list logo
