On 9/8/19 6:27 PM, Xianwen Chen (陈贤文) via arch-general wrote:
> For example,
>
> $ sudo pacrepairfile --uid --gid --mode --mtime
> /usr/lib/tmpfiles.d/colord.conf
>
> outputs
>
> /usr/lib/tmpfiles.d/colord.conf: set uid to 0
> /usr/lib/tmpfiles.d/colord.conf: set gid to 0
> warning:
Dear Eli,
Thank you.
I wrote a regulation expression, which extracts file name and path from
the output of paccheck:
$ sudo paccheck --file-properties --quiet | grep -Po "(?<=\').*(?=\')" |
sudo pacrepairfile --uid --gid --mode --mtime
However, somehow pacrepairfile was not working.
For e
On 9/8/19 4:40 PM, Xianwen Chen (陈贤文) via arch-general wrote:
> Dear Eli,
>
> Thank you!
>
> Is there a way to ask paccheck to list only files that need to be fixed?
>
> For example, if I run
>
> sudo paccheck --file-properties --quiet
>
> I get list of files with package information and e
Dear Eli,
Thank you!
Is there a way to ask paccheck to list only files that need to be fixed?
For example, if I run
sudo paccheck --file-properties --quiet
I get list of files with package information and error information, such as
screen: '/usr/lib/tmpfiles.d/screen.conf' permission
Dear Ralph,
Great! Thank you very much for the tips!
Yours sincerely,
Xianwen
On 08/09/2019 15.11, Ralph Corderoy wrote:
Dear Xianwen,
there are quite many files on my system that had wrong permissions or
GID's.
Perhaps there's been an errant recursive chmod or chgrp in the past by
root.
On 9/8/19 8:21 AM, Xianwen Chen (陈贤文) via arch-general wrote:
> Dear Ralph and Eli,
>
> Thank you.
>
> As Ralph suspected, there are quite many files on my system that had
> wrong permissions or GID's.
>
> Is there a way to automatically correct all the permissions and GID's?
Once more from the
On 9/8/19 7:59 AM, Ralph Corderoy wrote:
> $ sudo -i paccheck --file-properties atop
> atop: '/var/log/atop/dummy_after' permission mismatch (expected 644)
> atop: '/var/log/atop/dummy_after' modification time mismatch
> (expected 2019-02-06 20:
Topic: Email
Suggest: New package for officia repo [2]
MTA-STS is taking off and the major email providers are supporting it.
Details are described in RFC8461 [1] from Sep 2018.
As of now it has support by Google (gmail), yahoo, comcast, hotmail and
others.
MTA-STS is a new standard that aims
Dear Xianwen,
> there are quite many files on my system that had wrong permissions or
> GID's.
Perhaps there's been an errant recursive chmod or chgrp in the past by
root.
> Is there a way to automatically correct all the permissions and GID's?
Others like Eli might know an mtree-specific way,
Dear Ralph and Eli,
Thank you.
As Ralph suspected, there are quite many files on my system that had
wrong permissions or GID's.
Is there a way to automatically correct all the permissions and GID's?
Yours sincerely,
Xianwen
On 08/09/2019 11.28, Eli Schwartz via arch-general wrote:
On 9/8/
Hi Eli,
> > warning: atop: /var/log/atop/dummy_after (Permissions mismatch)
> ...
> > Not every error means the file on disk must be changed, perhaps it's
> > a packaging problem
>
> pacman -S pacutils && paccheck --file-properties
Thanks.
$ sudo -i paccheck --file-properties atop
at
Hello all,
I am using plain linux kernel 5.2.13 with proprietary nvidia driver 435.21
on my Nvidia Optimus (UHD 630 + 1050 Ti) notebook. Nothing fancy here and
everything is up to date but in order to utilize HDMI audio over Nvidia
card, I have to use this fix:
https://wiki.archlinux.org/index.php
On 9/8/19 5:20 AM, Ralph Corderoy wrote:
> Dear Xianwen,
>
>> After searching on-line, it seemed that similar problems were reported
>> by other users of systemd. The fix is to set owner of / as root.root.
>> I tried the solution and it worked!
>
> I'm glad you fixed it. / not being root:root i
Dear Xianwen,
> After searching on-line, it seemed that similar problems were reported
> by other users of systemd. The fix is to set owner of / as root.root.
> I tried the solution and it worked!
I'm glad you fixed it. / not being root:root is strange. You may wish
to
sudo -i pacman -Qqk
14 matches
Mail list logo
