CleanMasonCache - Revision history

Barton: /* FreeBSD */ Improve code formatting

2018-09-24T12:44:27Z

FreeBSD: Improve code formatting

← Older revision		Revision as of 07:44, 24 September 2018
Line 52:		Line 52:
	In [[FreeBSD]], all third-party software is installed in /usr/local/, so the command would be:		In [[FreeBSD]], all third-party software is installed in /usr/local/, so the command would be:

	rm -rf /usr/local/rt3/var/mason_data/obj/*		rm -rf /usr/local/rt3/var/mason_data/obj/*

	except for recent RT4 portbuild, where the RT var directory becomes /var/run/rt40		except for recent RT4 portbuild, where the RT var directory becomes /var/run/rt40

	So the command is rm -rf /var/run/rt40/mason_data/obj/*		So the command is

			rm -rf /var/run/rt40/mason_data/obj/*

	== Debian & Ubuntu ==		== Debian & Ubuntu ==

Barton: /* Debian & Ubuntu */ improve code formatting

2018-09-24T12:43:17Z

Debian & Ubuntu: improve code formatting

← Older revision		Revision as of 07:43, 24 September 2018
Line 64:		Line 64:
	It may also be useful to know that [[DevelMode]] requires a Perl module called Module::Refresh, a package for which is not easily found. So if you're hacking on something and want to see the changes, you can clear the cache and restart Apache in one go like so:		It may also be useful to know that [[DevelMode]] requires a Perl module called Module::Refresh, a package for which is not easily found. So if you're hacking on something and want to see the changes, you can clear the cache and restart Apache in one go like so:

	find /var/cache/request-tracker3.4/mason_data/ -type f -print0 \| xargs -0 rm -f ; /etc/init.d/apache2 restart		find /var/cache/request-tracker3.4/mason_data/ -type f -print0 \| xargs -0 rm -f ; /etc/init.d/apache2 restart

	== For developers ==		== For developers ==

	The [[DevelMode]] option allows you to avoid this step, but note that you don't want to use this option in production environment.		The [[DevelMode]] option allows you to avoid this step, but note that you don't want to use this option in production environment.

Barton: /* RedHat / CentOS */ improve code formatting

2018-09-24T12:42:04Z

RedHat / CentOS: improve code formatting

← Older revision		Revision as of 07:42, 24 September 2018
Line 13:		Line 13:
	'''Scripted:'''		'''Scripted:'''

	unset _response		<pre>
	_rt=$(find /opt /usr -name mason_data)		unset _response
			_rt=$(find /opt /usr -name mason_data)
	while [[ ( ${_response} != 'n' ) && ( ${_response} != 'N' ) && ( ${_response} != 'y' ) && ( ${_response} != 'Y' ) ]]; do
	read -p "Clearing mason cache in ${_rt}, continue? 'y/N': " _response		while [[ ( ${_response} != 'n' ) && ( ${_response} != 'N' ) && ( ${_response} != 'y' ) && ( ${_response} != 'Y' ) ]]; do
	done		read -p "Clearing mason cache in ${_rt}, continue? 'y/N': " _response
			done
	if [[ ( ${_response} == 'y' ) \|\| ( ${_response} == 'Y' ) ]]; then
	{		if [[ ( ${_response} == 'y' ) \|\| ( ${_response} == 'Y' ) ]]; then
	echo -n "Clearing mason cache in ${_rt}: "		{
	rm -rf ${_rt}/obj/*		echo -n "Clearing mason cache in ${_rt}: "
	_status=${?}		rm -rf ${_rt}/obj/*
			_status=${?}
	if [[ ${_status} == 0 ]]; then
	{		if [[ ${_status} == 0 ]]; then
	echo "[ SUCCESS ]"		{
	}		echo "[ SUCCESS ]"
	else		}
	{		else
	echo "[ FAIL ]"		{
	}		echo "[ FAIL ]"
	fi		}
	}		fi
	else		}
	{		else
	echo 'Exiting without clearning mason cache'		{
	}		echo 'Exiting without clearning mason cache'
	fi		}
			fi
			</pre>

	== SUSE/openSUSE ==		== SUSE/openSUSE ==

Admin: 7 revisions imported

2016-04-06T20:03:25Z

7 revisions imported

← Older revision		Revision as of 15:03, 6 April 2016
(No difference)

66.162.75.2: Added instructions for clearing cache for RHEL/Cent

2014-04-16T19:31:31Z

Added instructions for clearing cache for RHEL/Cent

New page

Each file in the <code>share/html</code> directory is a mason component. Mason precompiles these files into Perl code and stores precompiled files in the cache dir. This feature speeds up processing as it doesn't need to recompile components each time. Also we can turn off checks on the original components if recompilation is required. Skipping such tests is done to speed up things more. RT uses both of these features. So when you change anything in the <code>share/html</code> or <code>local/html</code> directories, you '''must clear the mason cache''' to see changes. To clear the cache, run this command:

shell> rm -rf /opt/rt3/var/mason_data/obj/*

'''NOTE''' Your path to RT may differ if you're using a packaged version of RT. Please, enter below paths for your OS distribution.
== RedHat / CentOS ==
'''Manual:'''

Locate your RT install directory, in our case /usr/local/rt4
rm -Rf /usr/local/rt4/var/mason_data/obj/*

'''Scripted:'''

unset _response
_rt=$(find /opt /usr -name mason_data)

while [[ ( ${_response} != 'n' ) && ( ${_response} != 'N' ) && ( ${_response} != 'y' ) && ( ${_response} != 'Y' ) ]]; do
read -p "Clearing mason cache in ${_rt}, continue? 'y/N': " _response
done

if [[ ( ${_response} == 'y' ) || ( ${_response} == 'Y' ) ]]; then
{
echo -n "Clearing mason cache in ${_rt}: "
rm -rf ${_rt}/obj/*
_status=${?}

if [[ ${_status} == 0 ]]; then
{
echo "[ SUCCESS ]"
}
else
{
echo "[ FAIL ]"
}
fi
}
else
{
echo 'Exiting without clearning mason cache'
}
fi
== SUSE/openSUSE ==

Assuming you have installed RT via the <code>request-tracker</code> package (as you should have), just run the <code>/usr/sbin/rt-clean-mason-cache</code> script as <code>root</code>.

== FreeBSD ==

In [[FreeBSD]], all third-party software is installed in /usr/local/, so the command would be:

rm -rf /usr/local/rt3/var/mason_data/obj/*

except for recent RT4 portbuild, where the RT var directory becomes /var/run/rt40

So the command is rm -rf /var/run/rt40/mason_data/obj/*

== Debian & Ubuntu ==

If you're using Debian packages then the filesystem location mentioned above is more likely to be /var/cache/request-tracker3.4/mason_data

It may also be useful to know that [[DevelMode]] requires a Perl module called Module::Refresh, a package for which is not easily found. So if you're hacking on something and want to see the changes, you can clear the cache and restart Apache in one go like so:

find /var/cache/request-tracker3.4/mason_data/ -type f -print0 | xargs -0 rm -f ; /etc/init.d/apache2 restart

== For developers ==

The [[DevelMode]] option allows you to avoid this step, but note that you don't want to use this option in production environment.

89.206.173.242: /* FreeBSD */

2013-07-18T16:03:14Z

FreeBSD

← Older revision		Revision as of 11:03, 18 July 2013
Line 16:		Line 16:
	rm -rf /usr/local/rt3/var/mason_data/obj/*		rm -rf /usr/local/rt3/var/mason_data/obj/*

	except for recent RT4 portbuild, where the ~~software is now located in~~ /var/run/		except for recent RT4 portbuild, where the RT var directory becomes /var/run/rt40

	So the command is rm -rf /var/run/rt40/mason_data/obj/*		So the command is rm -rf /var/run/rt40/mason_data/obj/*

89.206.173.242: /* FreeBSD */

2013-07-18T15:51:56Z

FreeBSD

New page

Each file in the <code>share/html</code> directory is a mason component. Mason precompiles these files into Perl code and stores precompiled files in the cache dir. This feature speeds up processing as it doesn't need to recompile components each time. Also we can turn off checks on the original components if recompilation is required. Skipping such tests is done to speed up things more. RT uses both of these features. So when you change anything in the <code>share/html</code> or <code>local/html</code> directories, you '''must clear the mason cache''' to see changes. To clear the cache, run this command:

shell> rm -rf /opt/rt3/var/mason_data/obj/*

'''NOTE''' Your path to RT may differ if you're using a packaged version of RT. Please, enter below paths for your OS distribution.

== SUSE/openSUSE ==

Assuming you have installed RT via the <code>request-tracker</code> package (as you should have), just run the <code>/usr/sbin/rt-clean-mason-cache</code> script as <code>root</code>.

== FreeBSD ==

In [[FreeBSD]], all third-party software is installed in /usr/local/, so the command would be:

rm -rf /usr/local/rt3/var/mason_data/obj/*

except for recent RT4 portbuild, where the software is now located in /var/run/

So the command is rm -rf /var/run/rt40/mason_data/obj/*

== Debian & Ubuntu ==

If you're using Debian packages then the filesystem location mentioned above is more likely to be /var/cache/request-tracker3.4/mason_data

It may also be useful to know that [[DevelMode]] requires a Perl module called Module::Refresh, a package for which is not easily found. So if you're hacking on something and want to see the changes, you can clear the cache and restart Apache in one go like so:

find /var/cache/request-tracker3.4/mason_data/ -type f -exec rm -f {} \;; /etc/init.d/apache2 restart

== For developers ==

The [[DevelMode]] option allows you to avoid this step, but note that you don't want to use this option in production environment.

Ghoti at 19:37, 27 January 2009

2009-01-27T19:37:50Z

New page