On Fri, 31 Jul 2020 05:51:21 +0800
Ed Greshko wrote:
> Well, it seems similar issues have come up in the past.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1309108
>
> and
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1298192
>
> You may want to try the work around in comment 19 of that
On 2020-07-31 01:25, stan via users wrote:
> On Thu, 30 Jul 2020 05:09:30 +0800
> Ed Greshko wrote:
>
>> Have you considered doing a relabel?
>>
>> fixfiles -F onboot
>>
>> and reboot?
> I tried a touch /.autorelabel and reboot but it followed symbolic links,
> and I have a bunch of links in /home
On Thu, 30 Jul 2020 05:09:30 +0800
Ed Greshko wrote:
> Have you considered doing a relabel?
>
> fixfiles -F onboot
>
> and reboot?
I tried a touch /.autorelabel and reboot but it followed symbolic links,
and I have a bunch of links in /home and /mnt. So I stopped it. It
looks like I can rest
On 2020-07-30 04:29, stan via users wrote:
> I reinstalled all the selinux components, and still the problem
> persists. I'm going to drop this for a while, see if anything comes to
> me. I have your workaround for the time being.
Have you considered doing a relabel?
fixfiles -F onboot
and reb
On Thu, 30 Jul 2020 02:47:22 +0800
Ed Greshko wrote:
>
> In the above, is PID 5954 the crond process? If you run ps with the
> -Z option do you get something like
>
> [egreshko@f31k ~]$ ps p 821 -Z
> LABEL PID TTY STAT TIME COMMAND
> system_u:system_r:crond
On 2020-07-29 23:25, stan via users wrote:
> On Wed, 29 Jul 2020 20:54:38 +0800
> Ed Greshko wrote:
>
>> So, dwatch is not part of Fedora.
> Not now.
Right. It was retired around F24 and you've rebuilt it locally to make a F31
package.
>> Well, you should easily be able to tell if the hourly c
On Wed, 29 Jul 2020 20:54:38 +0800
Ed Greshko wrote:
> So, dwatch is not part of Fedora.
Not now.
> On an F31 system...
>
> [egreshko@f31k ~]$ dnf info dwatch
> Last metadata expiration check: 0:00:33 ago on Wed 29 Jul 2020
> 08:49:46 PM CST. Error: No matching Packages to list
>
> On an F32
On 2020-07-29 20:29, stan via users wrote:
> On Wed, 29 Jul 2020 05:38:29 +0800
> Ed Greshko wrote:
>
>> On 2020-07-29 03:23, stan via users wrote:
>>> On Tue, 28 Jul 2020 10:35:54 -0700
>>> stan via users wrote:
>>>
Before I open a bugzilla, I wanted to check if anyone has an
explana
On Wed, 29 Jul 2020 05:38:29 +0800
Ed Greshko wrote:
> On 2020-07-29 03:23, stan via users wrote:
> > On Tue, 28 Jul 2020 10:35:54 -0700
> > stan via users wrote:
> >
> >> Before I open a bugzilla, I wanted to check if anyone has an
> >> explanation for this, and a fix.
> > Opened a bugzilla
On 2020-07-29 03:23, stan via users wrote:
> On Tue, 28 Jul 2020 10:35:54 -0700
> stan via users wrote:
>
>> Before I open a bugzilla, I wanted to check if anyone has an
>> explanation for this, and a fix.
> Opened a bugzilla,
> https://bugzilla.redhat.com/show_bug.cgi?id=1861505
Could you clarif
On Tue, 28 Jul 2020 10:35:54 -0700
stan via users wrote:
> Before I open a bugzilla, I wanted to check if anyone has an
> explanation for this, and a fix.
Opened a bugzilla,
https://bugzilla.redhat.com/show_bug.cgi?id=1861505
___
users mailing list --
On Tue, 28 Jul 2020 11:53:15 -0700
Samuel Sieb wrote:
> On 7/28/20 10:35 AM, stan via users wrote:
> > Recently, I've noticed that some jobs that are started by dwatch,
> > aren't starting. If I start them manually, they start fine.
> > dwatch is
>
> What is "dwatch". I can't find any refere
On 7/28/20 10:35 AM, stan via users wrote:
Recently, I've noticed that some jobs that are started by dwatch,
aren't starting. If I start them manually, they start fine. dwatch is
What is "dwatch". I can't find any reference to it (other than BSD).
On 7/28/20 10:35 AM, stan via users wrote:
Recently, I've noticed that some jobs that are started by dwatch,
aren't starting. If I start them manually, they start fine. dwatch is
in cron.d, and should be running every 5 minutes, but no cron jobs are
running. I see the following in journalctl,
Recently, I've noticed that some jobs that are started by dwatch,
aren't starting. If I start them manually, they start fine. dwatch is
in cron.d, and should be running every 5 minutes, but no cron jobs are
running. I see the following in journalctl,
Jul 28 10:07:08 localhost.localdomain crond[1
15 matches
Mail list logo
