Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Critical permission problem, bad chown in maraschino script #845
I have been running the latest xbian and after weeks, after installing more software, my setup stop working, kodi would not start and i'm in the login prompt.
After some checks, i found that all the RPi2 is now own by root and all SUID programs lost their special bit... it looked like something made a
I reset the permissions the best i could (
And after a new boot, i found that the /etc/rc2.d/S03maraschino is doing a
The maraschino package i have installed is :
So looking around i see 2 problems:
So please quickly fix the maraschino package to set a proper /etc/default/maraschino, so other setups where maraschino is installed aren't destroyed on the next boot
what do you have in /etc/default/maraschino , in the PID file?
i had /tmp/maraschino.pid ... maybe one setting from a older versions, i didn't updated my xbian for almost one year
If the current default is correct, then maybe moving the btrfs subvolumes out of /tmp is the only needed fix... as the tmp looks like a dangerous place to place the machine volumes, just in case another tool makes the wrong command. /media/btrfs looks lot better for me
I haven't changed anything from default installation, so PID points to /tmp folder
There are no subvolumes mounted under /tmp, /tmp is part of root subvolume
ok, so your setup is also doing a chown -R root /tmp in the maraschino init script ... and that may not always the the best thing to do, as other apps may already exist there with different permissions, so i think that using /tmp/maraschino.pid as the pid is a bad idea, use a subfolder, or use the default /run/maraschino/marachino.pid as a safer setup
as the btrfs, i have in /tmp/tmp.??????/@* folders that are the btrfs sub-volumes... i will try to find where they are coming from, but i do not recall setting up anything to mount those sub-volumes on boot
Agree, this is really not a good idea, IMO the init script isn't the best choice. It seems to be a 1:1 copy of the original script https://github.com/mrkipling/maraschino/blob/master/initd, and for my understanding
is wrong, because
Ahhh, now we're coming closer to the problem. Yeah, that mount remains sometimes after boot. I wasn't successful in my investigation where this came from. Same happens here, but never if initramfs is not used. So it must be inside of initramfs scripts, but could not find anything there.