phazon wrote: > Robin Bowes Wrote: >> That means slimserver can't connect to mysql. >> >> Can you see that mysql is running (after starting slimserver) ? >> >> Try this from a terminal; >> >> ps -ef | grep -i mysql >> >> R. > > Thanks for the reply. Yes I can see mysql... > > -root 4792 1 0 Jul02 ? 00:00:00 /bin/sh > /usr/bin/mysqld_safe > mysql 4832 4792 0 Jul02 ? 00:00:54 /usr/sbin/mysqld > --basedir=/usr --datadir=/var/lib/mysql --user=mysql > --pid-file=/var/run/mysqld/mysqld.pid --sk ip-locking --port=3306 > --socket=/var/run/mysqld/mysqld.sock > root 4833 4792 0 Jul02 ? 00:00:00 logger -p daemon.err -t > mysqld_s afe -i -t mysqld > 110 5146 4960 0 Jul02 ? 00:00:56 /usr/sbin/mysqld > --defaults-file =/var/cache/slimserver/my.cnf > --pid-file=/var/cache/slimserver/slimserver-mysql. pid > --log=/var/log/slimserver/slimserver.log > nick 3907 3888 0 12:28 pts/0 00:00:00 grep -i mysql > - > > Something I've just realised is all the tracks are on an NTFS-formatted > drive - could this be causing a problem? > >
What version of slimserver is this? R. _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/unix
