<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="bbPress/1.1-alpha-2855" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Austin Matzko&#039;s Forum &#187; Tag: files - Recent Posts</title>
		<link>http://austinmatzko.com/forum/tags/files</link>
		<description>Austin Matzko&#039;s Forum &#187; Tag: files - Recent Posts</description>
		<language>en-US</language>
		<pubDate>Sat, 11 Feb 2012 17:39:44 +0000</pubDate>
		<generator>http://bbpress.org/?v=1.1-alpha-2855</generator>
		<textInput>
			<title><![CDATA[Search]]></title>
			<description><![CDATA[Search all topics from these forums.]]></description>
			<name>q</name>
			<link>http://austinmatzko.com/forum/search.php</link>
		</textInput>
		<atom:link href="http://austinmatzko.com/forum/rss/tags/files" rel="self" type="application/rss+xml" />

		<item>
			<title>slshimerdla on "Very odd info being shown in the SQL files"</title>
			<link>http://austinmatzko.com/forum/topic/very-odd-info-being-shown-in-the-sql-files#post-3848</link>
			<pubDate>Mon, 22 Sep 2008 12:05:05 +0000</pubDate>
			<dc:creator>slshimerdla</dc:creator>
			<guid isPermaLink="false">3848@http://austinmatzko.com/forum/</guid>
			<description><p>Oh my goodness, you're so right!  I'm so sorry for bothering you.  Feel free to delete this thread.  I could've sworn I was using yours!  I will probably switch, then, if I can't get this answered. :)</p>
<p>Thanks so much, and sorry again!
</p></description>
		</item>
		<item>
			<title>filosofo on "Very odd info being shown in the SQL files"</title>
			<link>http://austinmatzko.com/forum/topic/very-odd-info-being-shown-in-the-sql-files#post-3847</link>
			<pubDate>Mon, 22 Sep 2008 11:41:27 +0000</pubDate>
			<dc:creator>filosofo</dc:creator>
			<guid isPermaLink="false">3847@http://austinmatzko.com/forum/</guid>
			<description><p>I think you must be confusing <a href="http://www.ilfilosofo.com/blog/wp-db-backup/">WP-DB-Backup</a> with another plugin.  WP-DB-Backup does not use mysqldump, although I think some other backup plugins do.
</p></description>
		</item>
		<item>
			<title>slshimerdla on "Very odd info being shown in the SQL files"</title>
			<link>http://austinmatzko.com/forum/topic/very-odd-info-being-shown-in-the-sql-files#post-3846</link>
			<pubDate>Mon, 22 Sep 2008 11:05:19 +0000</pubDate>
			<dc:creator>slshimerdla</dc:creator>
			<guid isPermaLink="false">3846@http://austinmatzko.com/forum/</guid>
			<description><p>Hey there! I am having some trouble with the WP-DB-Backup plugin.  I have it installed and running correctly.  It is sensing the locations of mysql and mysqldump automatically, and it is making backup SQL files in the backup-db folder..</p>
<p>The problem is what is within the contents of those backups.  In fact, if I hadn't gone to check the contents of those files, I would have never known that something was wrong.</p>
<p>Here's what's in the file (and I'm going to put the whole thing here, because it might help):</p>
<p><code>mysqldump  Ver 8.23 Distrib 3.23.58, for redhat-linux-gnu (i386)<br />
By Igor Romanenko, Monty, Jani &#38; Sinisa<br />
This software comes with ABSOLUTELY NO WARRANTY. This is free software,<br />
and you are welcome to modify and redistribute it under the GPL license</p>
<p>Dumping definition and data mysql database or table<br />
Usage: mysqldump [OPTIONS] database [tables]<br />
OR     mysqldump [OPTIONS] --databases [OPTIONS] DB1 [DB2 DB3...]<br />
OR     mysqldump [OPTIONS] --all-databases [OPTIONS]</p>
<p>  -A, --all-databases   Dump all the databases. This will be same as<br />
		        --databases with all databases selected.<br />
  -a, --all		Include all MySQL specific create options.<br />
  -#, --debug=...       Output debug log. Often this is 'd:t:o,filename`.<br />
  --character-sets-dir=...<br />
                        Directory where character sets are<br />
  -?, --help		Display this help message and exit.<br />
  -B, --databases       To dump several databases. Note the difference in<br />
			usage; In this case no tables are given. All name<br />
			arguments are regarded as databasenames.<br />
			'USE db_name;' will be included in the output<br />
  -c, --complete-insert Use complete insert statements.<br />
  -C, --compress        Use compression in server/client protocol.<br />
  --default-character-set=...<br />
                        Set the default character set<br />
  -e, --extended-insert Allows utilization of the new, much faster<br />
                        INSERT syntax.<br />
  --add-drop-table	Add a 'drop table' before each create.<br />
  --add-locks		Add locks around insert statements.<br />
  --allow-keywords	Allow creation of column names that are keywords.<br />
  --delayed-insert      Insert rows with INSERT DELAYED.<br />
  --delete-master-logs  Issue RESET MASTER on the master just after taking<br />
                        the dump, and before unlocking tables.<br />
                        This will automatically enable --first-slave.<br />
  --master-data         This will cause the master position and filename to<br />
                        be appended to your output, before unlocking tables.<br />
                        This will automatically enable --first-slave.<br />
  -F, --flush-logs	Flush logs file in server before starting dump.<br />
  -f, --force		Continue even if we get an sql-error.<br />
  -h, --host=...	Connect to host.<br />
  -l, --lock-tables     Lock all tables for read.<br />
  --no-autocommit       Wrap tables with autocommit/commit statements.<br />
  -K, --disable-keys   '/*!40000 ALTER TABLE tb_name DISABLE KEYS */;<br />
                        and '/*!40000 ALTER TABLE tb_name ENABLE KEYS */;<br />
                        will be put in the output.<br />
  -n, --no-create-db    'CREATE DATABASE /*!32312 IF NOT EXISTS*/ db_name;'<br />
                        will not be put in the output. The above line will<br />
                        be added otherwise, if --databases or<br />
                        --all-databases option was given.<br />
  -t, --no-create-info	Don't write table creation info.<br />
  -d, --no-data		No row information.<br />
  -O, --set-variable var=option<br />
                        give a variable a value. --help lists variables<br />
  --opt			Same as --add-drop-table --add-locks --all --quick<br />
                        --extended-insert --lock-tables --disable-keys<br />
  -p, --password[=...]	Password to use when connecting to server.<br />
                        If password is not given it's solicited on the tty.</p>
<p>  -P, --port=...	Port number to use for connection.<br />
  -q, --quick		Don't buffer query, dump directly to stdout.<br />
  -Q, --quote-names	Quote table and column names with `<br />
  -r, --result-file=... Direct output to a given file. This option should be<br />
                        used in MSDOS, because it prevents new line '\n'<br />
                        from being converted to '\n\r' (newline + carriage<br />
                        return).<br />
  -S, --socket=...	Socket file to use for connection.<br />
  --tables              Overrides option --databases (-B).<br />
  -T, --tab=...         Creates tab separated textfile for each table to<br />
                        given path. (creates .sql and .txt files).<br />
                        NOTE: This only works if mysqldump is run on<br />
                              the same machine as the mysqld daemon.<br />
  -u, --user=#		User for login if not current user.<br />
  -v, --verbose		Print info about the various stages.<br />
  -V, --version		Output version information and exit.<br />
  -w, --where=		dump only selected records; QUOTES mandatory!<br />
  -X, --xml             dump a database as well formed XML<br />
  -x, --first-slave     Locks all tables across all databases.<br />
  EXAMPLES: "--where=user='jimf'" "-wuserid&#62;1" "-wuserid&#60;1"<br />
  Use -T (--tab=...) with --fields-...<br />
  --fields-terminated-by=...<br />
                        Fields in the textfile are terminated by ...<br />
  --fields-enclosed-by=...<br />
                        Fields in the importfile are enclosed by ...<br />
  --fields-optionally-enclosed-by=...<br />
                        Fields in the i.file are opt. enclosed by ...<br />
  --fields-escaped-by=...<br />
                        Fields in the i.file are escaped by ...<br />
  --lines-terminated-by=...<br />
                        Lines in the i.file are terminated by ...</p>
<p>Default options are read from the following files in the given order:<br />
/etc/my.cnf /var/lib/mysql/my.cnf ~/.my.cnf<br />
The following groups are read: mysqldump client<br />
The following options may be given as the first argument:<br />
--print-defaults	Print the program argument list and exit<br />
--no-defaults		Don't read default options from any options file<br />
--defaults-file=#	Only read default options from the given file #<br />
--defaults-extra-file=# Read this file after the global files are read</p>
<p>Possible variables for option --set-variable (-O) are:<br />
max_allowed_packet    current value: 25165824<br />
net_buffer_length     current value: 1047551<br />
[/code]</p>
<p>It's like it's showing me the information about mysqldump in the file instead of backing up the database.  I don't have a clue as to why this would be happening.</p>
<p>However, a bit of background.  The website is being hosted by GoDaddy (ugh), and I've been told by them that even though they now allow cron jobs on shared hosting, I cannot use a cron job directly in their cpanel in order to do a database backup.  They assured me that doing a database backup through PHP code would still work, however.  Perhaps they were wrong, and it's doing this because it won't let me access mysqldump?</p>
<p>I'd appreciate any help I can get with this, thank you very much!</code>
</p></description>
		</item>

	</channel>
</rss>

