Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#24533 - [dcron] crontab isn't flagged as an executable

Attached to Project: Arch Linux
Opened by alex (alexkral) - Wednesday, 01 June 2011, 15:35 GMT
Last edited by Eric Belanger (Snowman) - Wednesday, 01 June 2011, 21:56 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Backintime (and possible some other programs) is confused because the /usr/bin/crontab script isn't tagged as an executable. It can be fixed with doing so manually.
I don't think it's a bug of backintime because every script should be tagged as an executable.

somehow this problem seems just to appear in one of my systems. Perhaps it's caused by an another programm.
This task depends upon

Closed by  Eric Belanger (Snowman)
Wednesday, 01 June 2011, 21:56 GMT
Reason for closing:  Not a bug
Comment by Eric Belanger (Snowman) - Wednesday, 01 June 2011, 16:27 GMT
It's an executable on my system:
$ ls -l /usr/bin/crontab
-rwsr-xr-x 1 root root 40K May 4 17:07 /usr/bin/crontab

Does the permission gets fixed if you reinstall the package?
Comment by alex (alexkral) - Wednesday, 01 June 2011, 19:46 GMT
no, it appears again.
Somehow is the permission is wrong in the package.
here the getfacl output
before:
# file: usr/bin/crontab
# owner: root
# group: users
# flags: s--
user::rwx
group::r-x
other::---

after changing the permission
# owner: root
# group: users
# flags: s--
user::rwx
group::r-x
other::--x

I see the problem: others have no permission to execute the script; is it a security feature or is it a fault?

Comment by alex (alexkral) - Wednesday, 01 June 2011, 20:16 GMT
Ok, it was my fault:
my user account wasn't in the users group and it's a security issue to let everyone playing with the crontab.
I close the bug report.

sorry for any incovencieces. I should have tested it better.

Loading...