btmp should be root:root 0600. (wrong owner/group root:utmp)

Using openSUSE 12.1 (Asparagus) (x86_64)

When run SuSEconfig to check all working seeing :.


Checking permissions and ownerships - using the permissions files
    /etc/permissions
    /etc/permissions.easy
    /etc/permissions.d/mail-server
    /etc/permissions.d/postfix
    /etc/permissions.local
/var/log/btmp should be root:root 0600. (wrong owner/group root:utmp)
Finished.

To fix run


linux-xfp4:~ # **SuSEconfig --module permissions**
Starting SuSEconfig, the SuSE Configuration Tool...
Running module permissions only
Reading /etc/sysconfig and updating the system...
Executing /sbin/conf.d/SuSEconfig.permissions...
Checking permissions and ownerships - using the permissions files
    /etc/permissions
    /etc/permissions.easy
    /etc/permissions.d/mail-server
    /etc/permissions.d/postfix
    /etc/permissions.local
setting /var/log/btmp to root:root 0600. (wrong owner/group root:utmp)
Finished.

When run SuSEconfig again, it shows OK. Stays OK for a while, then problem returns, suspect after re-starts.

Searched, found and read: http://forums.opensuse.org/english/get-technical-help-here/tumbleweed/470674-zypper-broken.html

No other obvious problems, do we ignore this problem, or need be concerned and keep fixing, until opensuse technical brains have chance to deal with it ?

BTW am very happy with work of technical people (many/most volunteers), after all they keep NON-Technical types like self (or worse) happily online :slight_smile:

.

On 2012-07-03 09:16, paulparker wrote:

> To fix run
>
>
> Code:
> --------------------
>
> linux-xfp4:~ # SuSEconfig --module permissions

> setting /var/log/btmp to root:root 0600. (wrong owner/group root:utmp)
> Finished.
>
> --------------------
>
>
> When run SuSEconfig again, it shows OK. Stays OK for a while, then
> problem returns, suspect after re-starts.

Ah.

> Searched, found and read: http://tinyurl.com/cyq5xtl

Nothing really relevant there that I can see… :-?

It might be “/etc/logrotate.d/wtmp”. Today I don’t have a 12.1 to check
what it contains. If not, there is a trick with AA to learn who is causing
it, perhaps.

> No other obvious problems, do we ignore this problem, or need be
> concerned and keep fixing, until opensuse technical brains have chance
> to deal with it ?

For that you have to report it on bugzilla.

> BTW am very happy with work of technical people (many/most
> volunteers), after all they keep NON-Technical types like self (or
> worse) happily online :slight_smile:

Surprisingly, it works.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

On 07/03/2012 01:23 PM, Carlos E. R. wrote:
>> until opensuse technical brains have chance
>> >to deal with it ?
> For that you have to report it on bugzilla.

or if the technical level here is not enough to determine if a bug
should be raised, or not…you can sure ask on the mail list and
probably find a good answer

i guess it should be logged as a bug (if you are pretty darn sure
you have not wickered incorrectly a config somewhere that caused
this–but, Carlos is on both lists and didn’t say: “log a bug”…so, i
am probably wrong)

to ask on the mail list, i’d suggest you start by looking here:

http://en.opensuse.org/openSUSE:Communication_channels#Mailing_lists

and, read the stuff about “Mailing list netiquette” if you are not
already familiar with hacker society, and then subscribe to the
opensuse@opensuse.org list…

or, if you wanna just go ahead and jump into bugzilla you may (but if
you caused the problem . . .) by starting here:
http://tinyurl.com/nzhq7j

please do not report before you search…


dd