Find - Revision history

Hdridder at 13:10, 13 January 2026

2026-01-13T13:10:58Z

← Older revision		Revision as of 13:10, 13 January 2026
Line 44:		Line 44:
	-gid (group id)		-gid (group id)

	;<code>find <dir> -type d ~~-depth~~ -empty -delete</code>		;<code>find <dir> -depth -type d -empty -delete</code>
	:Find empty directories and delete them		:Find empty directories and delete them

Hdridder at 09:11, 6 November 2025

2025-11-06T09:11:39Z

← Older revision		Revision as of 09:11, 6 November 2025
Line 14:		Line 14:
	:For each file found execute <command> in the directory containing the file. {} represents the found file. NOTE!! Do not forget the \; at the end.		:For each file found execute <command> in the directory containing the file. {} represents the found file. NOTE!! Do not forget the \; at the end.
	: -exec works too but is less secure as mistakes main lead to execution in an unexpected place.		: -exec works too but is less secure as mistakes main lead to execution in an unexpected place.
			: If more commands need to be executed specify -exec <command> {} \; for each command.

	;<code>find <directory> -type f -mtime 1 </code>		;<code>find <directory> -type f -mtime 1 </code>

Hdridder at 06:26, 7 October 2025

2025-10-07T06:26:32Z

← Older revision		Revision as of 06:26, 7 October 2025
Line 42:		Line 42:
	-group (group name)		-group (group name)
	-gid (group id)		-gid (group id)

			;<code>find <dir> -type d -depth -empty -delete</code>
			:Find empty directories and delete them

Hdridder at 09:03, 7 August 2025

2025-08-07T09:03:09Z

← Older revision		Revision as of 09:03, 7 August 2025
Line 2:		Line 2:
	Find things in a directory tree		Find things in a directory tree

	;<code>find <directory> -type f -name '<~~spec~~>' </code>		;<code>find <directory> -type f -name '<pattern>' </code>
	:Find ~~file~~ in and below <directory> that match <~~spec~~>. Type f is for files, d for directory's, no type finds all.		:Find files in and below <directory> that match <pattern>. Type f is for files, d for directory's, no type finds all.

	;<code>find -L <directory~~> <spec~~>' </code>		;<code>find -L <directory>' </code>
	:Do follow symbolic links, default behavior is not to follow.		:Do follow symbolic links, default behavior is not to follow.

	;<code>find <directory> -xdev -name <~~spec~~>' </code>		;<code>find <directory> -xdev -name <pattern>' </code>
	:Limit the search to the current file-system, do not go into mounted filesystems.		:Limit the search to the current file-system, do not go into mounted filesystems.

	;<code>find <directory> -type f -name '<~~spec~~>' -execdir <command> {} \;</code>		;<code>find <directory> -type f -name '<pattern>' -execdir <command> {} \;</code>
	:For each file found execute <command> in the directory containing the file. {} represents the found file. NOTE!! Do not forget the \; at the end.		:For each file found execute <command> in the directory containing the file. {} represents the found file. NOTE!! Do not forget the \; at the end.
	: -exec works too but is less secure as mistakes main lead to execution in an unexpected place.		: -exec works too but is less secure as mistakes main lead to execution in an unexpected place.

	;<code>find <directory> -type f ~~-name '<spec>'~~ -mtime 1 </code>		;<code>find <directory> -type f -mtime 1 </code>
	:Find files modified 1 day ago (between 24 and 48 hours).		:Find files modified 1 day ago (between 24 and 48 hours).
	:Negative numbers find all files modified max 1 day ago.		:Negative numbers find all files modified max 1 day ago.
Line 21:		Line 21:
	:<code>-mmin</code> counts minutes instead of days.		:<code>-mmin</code> counts minutes instead of days.

	;<code>find <directory> -type f -~~name '~~<~~spec~~>' -printf '%T@ %p\n'</code>		;<code>find <directory> -type f -newer <filename></code>
			:Find files modified after the modification time of <filename>
			:You can set the modification time of <filename> like <code>touch -t YYYYmmddHHMM <filename></code>

			;<code>find <directory> -type f -printf '%T@ %p\n'</code>
	:Print the files modification times in [https://www.epochconverter.com/ epoch] (seconds since Jan 1, 1970) and the filename. Can be used e.g. to find the last files modified (with sort -n and tail)		:Print the files modification times in [https://www.epochconverter.com/ epoch] (seconds since Jan 1, 1970) and the filename. Can be used e.g. to find the last files modified (with sort -n and tail)

Hdridder at 13:20, 5 August 2025

2025-08-05T13:20:30Z

← Older revision		Revision as of 13:20, 5 August 2025
Line 4:		Line 4:
	;<code>find <directory> -type f -name '<spec>' </code>		;<code>find <directory> -type f -name '<spec>' </code>
	:Find file in and below <directory> that match <spec>. Type f is for files, d for directory's, no type finds all.		:Find file in and below <directory> that match <spec>. Type f is for files, d for directory's, no type finds all.

			;<code>find -L <directory> <spec>' </code>
			:Do follow symbolic links, default behavior is not to follow.

	;<code>find <directory> -xdev -name <spec>' </code>		;<code>find <directory> -xdev -name <spec>' </code>
	:Limit the search to the current file-system, to not go into mounted filesystems.		:Limit the search to the current file-system, do not go into mounted filesystems.

	;<code>find <directory> -type f -name '<spec>' -execdir <command> {} \;</code>		;<code>find <directory> -type f -name '<spec>' -execdir <command> {} \;</code>

Hdridder at 08:27, 2 October 2024

2024-10-02T08:27:22Z

← Older revision		Revision as of 08:27, 2 October 2024
Line 29:		Line 29:
	;<code>find <dir> -type f -inum <inode number> -delete</code>		;<code>find <dir> -type f -inum <inode number> -delete</code>
	:Find file by inode number and delete it. This can be used to removed files with weird names. This does not delete the inode, if files have more hardlinks all must be deleted.		:Find file by inode number and delete it. This can be used to removed files with weird names. This does not delete the inode, if files have more hardlinks all must be deleted.

			Other options to select specific files are (among many others):
			-user (username)
			-uid (user id)
			-group (group name)
			-gid (group id)

Hdridder at 13:31, 23 October 2022

2022-10-23T13:31:10Z

← Older revision		Revision as of 13:31, 23 October 2022
Line 26:		Line 26:
	;<code>find <dir> -type f -mtime +30 -ls\|awk 'BEGIN {} {totsize+=$7} END { print totsize/1000000}'</code>		;<code>find <dir> -type f -mtime +30 -ls\|awk 'BEGIN {} {totsize+=$7} END { print totsize/1000000}'</code>
	:Find the total size of all files older than 30 days.		:Find the total size of all files older than 30 days.

			;<code>find <dir> -type f -inum <inode number> -delete</code>
			:Find file by inode number and delete it. This can be used to removed files with weird names. This does not delete the inode, if files have more hardlinks all must be deleted.

Hdridder at 07:23, 13 May 2022

2022-05-13T07:23:05Z

← Older revision		Revision as of 07:23, 13 May 2022
Line 21:		Line 21:
	:Print the files modification times in [https://www.epochconverter.com/ epoch] (seconds since Jan 1, 1970) and the filename. Can be used e.g. to find the last files modified (with sort -n and tail)		:Print the files modification times in [https://www.epochconverter.com/ epoch] (seconds since Jan 1, 1970) and the filename. Can be used e.g. to find the last files modified (with sort -n and tail)

	; find <dir> -printf '%s %p\n'\| sort -nr \| head -10		;<code>find <dir> -printf '%s %p\n'\| sort -nr \| head -10</code>
	:Find the top 10 largest files under a directory		:Find the top 10 largest files under a directory

			;<code>find <dir> -type f -mtime +30 -ls\|awk 'BEGIN {} {totsize+=$7} END { print totsize/1000000}'</code>
			:Find the total size of all files older than 30 days.

Hdridder at 09:20, 2 March 2022

2022-03-02T09:20:00Z

← Older revision		Revision as of 09:20, 2 March 2022
Line 8:		Line 8:
	:Limit the search to the current file-system, to not go into mounted filesystems.		:Limit the search to the current file-system, to not go into mounted filesystems.

	;<code>find <directory> -type f -name '<spec>' -~~exec~~ <command> {} \;</code>		;<code>find <directory> -type f -name '<spec>' -execdir <command> {} \;</code>
	:For each file found execute <command> {} represents the found file. NOTE!! Do not forget the \; at the end.		:For each file found execute <command> in the directory containing the file. {} represents the found file. NOTE!! Do not forget the \; at the end.
			: -exec works too but is less secure as mistakes main lead to execution in an unexpected place.

	;<code>find <directory> -type f -name '<spec>' -mtime 1 </code>		;<code>find <directory> -type f -name '<spec>' -mtime 1 </code>

Hdridder at 16:38, 17 January 2021

2021-01-17T16:38:00Z

← Older revision		Revision as of 16:38, 17 January 2021
Line 18:		Line 18:

	;<code>find <directory> -type f -name '<spec>' -printf '%T@ %p\n'</code>		;<code>find <directory> -type f -name '<spec>' -printf '%T@ %p\n'</code>
	:Print the files modification times in epoch (seconds since Jan 1, 1970) and the filename. Can be used e.g. to find the last files modified (with sort -n and tail)		:Print the files modification times in [https://www.epochconverter.com/ epoch] (seconds since Jan 1, 1970) and the filename. Can be used e.g. to find the last files modified (with sort -n and tail)

	; find <dir> -printf '%s %p\n'\| sort -nr \| head -10		; find <dir> -printf '%s %p\n'\| sort -nr \| head -10
	:Find the top 10 largest files under a directory		:Find the top 10 largest files under a directory