**** BEGIN LOGGING AT Tue Apr 29 02:59:58 2008 Apr 29 06:44:31 is anyone using anything other than twonkyvision for streaming mp3s? Apr 29 08:34:06 hey Apr 29 08:34:15 I have done everything to try to get rid of this with mysql Apr 29 08:34:22 but whenever I try to start it, or reboot the slug Apr 29 08:34:26 I get this in the error log Apr 29 08:34:26 080429 4:32:01 [ERROR] /usr/libexec/mysqld: Can't create/write to file '/var/run/mysqld.pid' (Errcode: 13) Apr 29 08:34:26 080429 4:32:01 [ERROR] Can't start server: can't create PID file: Permission denied Apr 29 08:34:43 slugos/be Apr 29 08:36:09 DrJ: hm, looks like you cant write to /var/run/ Apr 29 08:36:26 I fix it, with chmod 766 /var/run Apr 29 08:36:28 DrJ: change that ;) Apr 29 08:36:36 but... Apr 29 08:36:38 if I reboot Apr 29 08:36:39 but? Apr 29 08:36:47 it goes back to what it was Apr 29 08:36:53 DrJ: is it in the ram-image? Apr 29 08:36:53 and I have to manually fix this issue again Apr 29 08:36:55 and start it Apr 29 08:36:59 which I sometimes forget to do Apr 29 08:37:03 idk Apr 29 08:37:16 DrJ: im totally not familiar with slugos and stuff, but i would just put it into your rc-level somewhere Apr 29 08:37:24 like a bootup script to prepare the env Apr 29 08:38:03 looks like that part (maybe because its written to a lot and temp-stuff) is held in the ram instead of physical storage space, so any changes are lost after reboot Apr 29 08:49:23 I don't really understand why mysqld has a problem writing to it Apr 29 08:49:29 should be running as root Apr 29 08:49:40 sure there is no special mysql-user? Apr 29 08:50:27 there is one mysql user named "mysql" Apr 29 08:50:33 but I think I created that Apr 29 08:50:53 well, maybe not Apr 29 08:50:59 his home directory is /var/mysql Apr 29 08:51:02 I didn't do that Apr 29 08:51:07 maybe if I change his group to root Apr 29 08:53:18 yah, maybe **** ENDING LOGGING AT Wed Apr 30 03:00:02 2008