MySQL & bootsync.sh

[nickjf20]

Hi,

I'm trying to get MySQL working so that databases and users are persistent across boot.

So far I have all the steps worked out manually as follows;

1. Create  a database and a user with full privileges to said database.
2. Copy over /path/to/my.cnf and /path/to/mysql to a location on my hdd
3. symlink said files on my hdd over to their 'correct' positions through bootsync.sh

I did have the symlink commands in bootlocal.sh to delete the auto generated my.cnf and mysql directory, and then symlink the hdd files over, but by this point the mysql daemon had already loaded and so didn't take the settings from my HDD files.

My problem is that I am scripting all this for ease of use, and a command such as

Code: [Select]

echo "ln -sf /mnt/sda1/lost+found/my.cnf /usr/local/etc/my.cnf" >> /opt/bootsync.sh
simply returns '-sh: can't create /opt/bootsync.sh: Permission denied'

Any ideas ? I tried restarting mysqld_safe when using the bootlocal.sh method, but this simply seems to stop mysql from working.

[Rich]

Hi nickjf20
I just checked the permissions for my bootsync.sh file and only root has write permission. Try using

sudo editor /opt/bootsync.sh

and place your commands where you want them.

[curaga]

There was some discussion with mysql auto-starting, with problems like that. I don't recall what the outcome was, but you can work around that in many ways - kill the autostarted instance, edit the extension not to autostart...

[Rich]

Hi nickjf20
I just reread your last post.

My problem is that I am scripting all this for ease of use, and a command such as

Code:
echo "ln -sf /mnt/sda1/lost+found/my.cnf /usr/local/etc/my.cnf" >> /opt/bootsync.sh

simply returns '-sh: can't create /opt/bootsync.sh: Permission denied'

Even if it worked it's a bad idea. Due to back up and restore, your bootsync file would start to grow
because you would keep on appending the same line over and over. Plus if bootsync is executing
at the time you should not be trying to write to it.

[nickjf20]

@Rich The problem has never been editing bootsync.sh through an editor such as nano, it's just that using echo to 'inject' lines of text into it doesn't work, even when run as root.

As for curaga's suggestion, when I run

Code: [Select]

/usr/local/bin/mysqld_safe restart as root and as tc, it 'breaks' mysql to the extent of no command working.

Please could you give me the correct commands ?

EDIT: just saw your last post -- the script (I can post it if you want) has checks to see whether it has been run before, so there is no chance of bootsync.sh growing out of proportion.

I have had a really good look round google, and all lead to the latest reply early july that the maintainer of MySQL.tcz will be updating it to 'fit in' with the tiny core persistence ethos.

[Rich]

Hi nickjf20

EDIT: just saw your last post -- the script (I can post it if you want) has checks to see whether it has been run before, so there is no chance of bootsync.sh growing out of proportion.

Then why not simply let that script create the link instead of having it append the command to bootsync?

[nickjf20]

The script doesn't run on boot and needs some other method of creating the symlinks on boot.

adding them to bootlocal.sh is too late in the booting process -- mysqld creates 'generic' my.cnf and databases which obviously do not contain my data !

I had it set to remove the generic DBs and then symlink mine in, but restarting mysql as above doesn't seem to work.

[Rich]

Hi nickjf20
See if something in this link is helpful.
http://forum.tinycorelinux.net/index.php?topic=7008.0

[nickjf20]

I hope to have it all worked out by tomorrow night -- I'll post back a definitive guide if you want it included in the wiki ?

[Rich]

Hi nickjf20
Additions to the Wiki are always welcome and appreciated.

[maro]

... The problem has never been editing bootsync.sh through an editor such as nano, it's just that using echo to 'inject' lines of text into it doesn't work, even when run as root. ...

nickjf20: The reason that sudo echo SOME_TEXT > FILE_OWNED_BY_ROOT fails when run in a shell of a non-root user is that the 'echo SOME_TEXT' gets executed as 'root' but the output redirection is handled by the shell (of the non-root user), which causes the "problem" you've observed.

If you still wonder how to solve this little problem in the future I'd like to suggest the following:
    echo SOME_TEXT | sudo tee FILE_OWNED_BY_ROOT > /dev/null
and when you want to append instead of overwriting just add the '-a' option to the 'tee' command. If you don't care about that 'SOME_TEXT' showing up as output somewhere you could also drop the output redirection (to '/dev/null').

An alternative suggestion would be to use sudo sh -c "echo SOME_TEXT > FILE_OWNED_BY_ROOT", but that can become tricky if your command would be more complicated than a simple 'echo' and you need quoting inside the double quotes. Not a "biggie" if one pays attention to it, but I at least have now developed a preference for the solution with the 'tee'.

[nickjf20]

http://wiki.tinycorelinux.net/wiki:mysql_persistence_guide

[Rich]

Hi nickjf20
Nice write up, very clear and concise. One minor point, under  Filetool method  the entries for
/opt/.filetool,lst  should not have a leading slash.