How can I get files using find command












2















How to use find command to get only files from the current directory (excluding subdirectories and its files) older than a day on AIX?






find aix







share|improve this question




















  • 3





    Please always mention your operating system! You already wasted your time on Ask Ubuntu because you didn't tell us you were using AIX and now you have reposted here (which is fine, AIX is welcome here) and you still didn't tell us you're using AIX! I had to edit it in. The basic tools like find vary considerably between the different implementations, so you always need to tell us what OS you are using. The shell you are using, ksh in your case, is irrelevant.

    – terdon♦
    15 hours ago
















2















How to use find command to get only files from the current directory (excluding subdirectories and its files) older than a day on AIX?






find aix







share|improve this question




















  • 3





    Please always mention your operating system! You already wasted your time on Ask Ubuntu because you didn't tell us you were using AIX and now you have reposted here (which is fine, AIX is welcome here) and you still didn't tell us you're using AIX! I had to edit it in. The basic tools like find vary considerably between the different implementations, so you always need to tell us what OS you are using. The shell you are using, ksh in your case, is irrelevant.

    – terdon♦
    15 hours ago














2












2








2








How to use find command to get only files from the current directory (excluding subdirectories and its files) older than a day on AIX?






find aix







share|improve this question
















How to use find command to get only files from the current directory (excluding subdirectories and its files) older than a day on AIX?






find aix




find aix






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 15 hours ago









terdon♦

132k32262441




132k32262441










asked 17 hours ago









AnonyAnony

1191




1191








  • 3





    Please always mention your operating system! You already wasted your time on Ask Ubuntu because you didn't tell us you were using AIX and now you have reposted here (which is fine, AIX is welcome here) and you still didn't tell us you're using AIX! I had to edit it in. The basic tools like find vary considerably between the different implementations, so you always need to tell us what OS you are using. The shell you are using, ksh in your case, is irrelevant.

    – terdon♦
    15 hours ago














  • 3





    Please always mention your operating system! You already wasted your time on Ask Ubuntu because you didn't tell us you were using AIX and now you have reposted here (which is fine, AIX is welcome here) and you still didn't tell us you're using AIX! I had to edit it in. The basic tools like find vary considerably between the different implementations, so you always need to tell us what OS you are using. The shell you are using, ksh in your case, is irrelevant.

    – terdon♦
    15 hours ago








3




3





Please always mention your operating system! You already wasted your time on Ask Ubuntu because you didn't tell us you were using AIX and now you have reposted here (which is fine, AIX is welcome here) and you still didn't tell us you're using AIX! I had to edit it in. The basic tools like find vary considerably between the different implementations, so you always need to tell us what OS you are using. The shell you are using, ksh in your case, is irrelevant.

– terdon♦
15 hours ago





Please always mention your operating system! You already wasted your time on Ask Ubuntu because you didn't tell us you were using AIX and now you have reposted here (which is fine, AIX is welcome here) and you still didn't tell us you're using AIX! I had to edit it in. The basic tools like find vary considerably between the different implementations, so you always need to tell us what OS you are using. The shell you are using, ksh in your case, is irrelevant.

– terdon♦
15 hours ago










1 Answer
1






active

oldest

votes


















10














Assuming that the implementation of find on your Unix has the -maxdepth predicate (it's non-standard, but often available), the following find command would do that:



find . -maxdepth 1 -type f -mtime +1


This would print the names of the regular files (i.e. not directories, sockets, named pipes etc.) whose modification timestamp was more than 24 hours ago to the terminal.



If -maxdepth can't be used, then consider



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -print


This means:




  1. If the current thing find is looking at is a directory (-type d), and

  2. If its name is not . (! -name .), i.e. it's a subdirectory, then


  3. Prune that directory from the search path of find (-prune). This stops find from even considering anything beneath subdirectories.


Otherwise (-o):




  1. If the thing is a regular file (-type f), and

  2. If its modification timestamp is older than 24 hours (-mtime +1), then

  3. Print the name of the thing we've found (-print).


The parentheses are there for precedence between the two sets of tests. They need to be escaped as they would otherwise be handled by the shell (as defining a sub-shell).



By default, find outputs the pathnames of the found files. This means that you'll get filenames prepended by ./ from the above command. If you don't want that, then you will have to call the basename utility for each found filename.



You can do that like this:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec basename {} ;


In comments you mention that you'd like to compress these files. For this, there is no need to call the basename utility. Just call gzip (or whatever compression utility you'd like to use) instead:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec gzip {} +


Depending on whether you'd like to do something further with these files, you may look for similar question on this site, e.g. Why is looping over find's output bad practice?



Also related:




  • Understanding the -exec option of `find`






share|improve this answer





















  • 2





    Comments are not for extended discussion; this conversation has been moved to chat.

    – terdon♦
    15 hours ago











  • Is there any way using xargs to implement the same?

    – Anony
    14 hours ago











  • @Anony Not in any way that would help I think. Also, this comment section was archived in a chat. Do consider using it. Also note that I've asked multiple times for the actual command that you are using. I can't debug anything without seeing it. Do not post further comments in this thread, but do feel welcome to use the chat.

    – Kusalananda
    14 hours ago













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506959%2fhow-can-i-get-files-using-find-command%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









10














Assuming that the implementation of find on your Unix has the -maxdepth predicate (it's non-standard, but often available), the following find command would do that:



find . -maxdepth 1 -type f -mtime +1


This would print the names of the regular files (i.e. not directories, sockets, named pipes etc.) whose modification timestamp was more than 24 hours ago to the terminal.



If -maxdepth can't be used, then consider



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -print


This means:




  1. If the current thing find is looking at is a directory (-type d), and

  2. If its name is not . (! -name .), i.e. it's a subdirectory, then


  3. Prune that directory from the search path of find (-prune). This stops find from even considering anything beneath subdirectories.


Otherwise (-o):




  1. If the thing is a regular file (-type f), and

  2. If its modification timestamp is older than 24 hours (-mtime +1), then

  3. Print the name of the thing we've found (-print).


The parentheses are there for precedence between the two sets of tests. They need to be escaped as they would otherwise be handled by the shell (as defining a sub-shell).



By default, find outputs the pathnames of the found files. This means that you'll get filenames prepended by ./ from the above command. If you don't want that, then you will have to call the basename utility for each found filename.



You can do that like this:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec basename {} ;


In comments you mention that you'd like to compress these files. For this, there is no need to call the basename utility. Just call gzip (or whatever compression utility you'd like to use) instead:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec gzip {} +


Depending on whether you'd like to do something further with these files, you may look for similar question on this site, e.g. Why is looping over find's output bad practice?



Also related:




  • Understanding the -exec option of `find`






share|improve this answer





















  • 2





    Comments are not for extended discussion; this conversation has been moved to chat.

    – terdon♦
    15 hours ago











  • Is there any way using xargs to implement the same?

    – Anony
    14 hours ago











  • @Anony Not in any way that would help I think. Also, this comment section was archived in a chat. Do consider using it. Also note that I've asked multiple times for the actual command that you are using. I can't debug anything without seeing it. Do not post further comments in this thread, but do feel welcome to use the chat.

    – Kusalananda
    14 hours ago


















10














Assuming that the implementation of find on your Unix has the -maxdepth predicate (it's non-standard, but often available), the following find command would do that:



find . -maxdepth 1 -type f -mtime +1


This would print the names of the regular files (i.e. not directories, sockets, named pipes etc.) whose modification timestamp was more than 24 hours ago to the terminal.



If -maxdepth can't be used, then consider



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -print


This means:




  1. If the current thing find is looking at is a directory (-type d), and

  2. If its name is not . (! -name .), i.e. it's a subdirectory, then


  3. Prune that directory from the search path of find (-prune). This stops find from even considering anything beneath subdirectories.


Otherwise (-o):




  1. If the thing is a regular file (-type f), and

  2. If its modification timestamp is older than 24 hours (-mtime +1), then

  3. Print the name of the thing we've found (-print).


The parentheses are there for precedence between the two sets of tests. They need to be escaped as they would otherwise be handled by the shell (as defining a sub-shell).



By default, find outputs the pathnames of the found files. This means that you'll get filenames prepended by ./ from the above command. If you don't want that, then you will have to call the basename utility for each found filename.



You can do that like this:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec basename {} ;


In comments you mention that you'd like to compress these files. For this, there is no need to call the basename utility. Just call gzip (or whatever compression utility you'd like to use) instead:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec gzip {} +


Depending on whether you'd like to do something further with these files, you may look for similar question on this site, e.g. Why is looping over find's output bad practice?



Also related:




  • Understanding the -exec option of `find`






share|improve this answer





















  • 2





    Comments are not for extended discussion; this conversation has been moved to chat.

    – terdon♦
    15 hours ago











  • Is there any way using xargs to implement the same?

    – Anony
    14 hours ago











  • @Anony Not in any way that would help I think. Also, this comment section was archived in a chat. Do consider using it. Also note that I've asked multiple times for the actual command that you are using. I can't debug anything without seeing it. Do not post further comments in this thread, but do feel welcome to use the chat.

    – Kusalananda
    14 hours ago
















10












10








10







Assuming that the implementation of find on your Unix has the -maxdepth predicate (it's non-standard, but often available), the following find command would do that:



find . -maxdepth 1 -type f -mtime +1


This would print the names of the regular files (i.e. not directories, sockets, named pipes etc.) whose modification timestamp was more than 24 hours ago to the terminal.



If -maxdepth can't be used, then consider



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -print


This means:




  1. If the current thing find is looking at is a directory (-type d), and

  2. If its name is not . (! -name .), i.e. it's a subdirectory, then


  3. Prune that directory from the search path of find (-prune). This stops find from even considering anything beneath subdirectories.


Otherwise (-o):




  1. If the thing is a regular file (-type f), and

  2. If its modification timestamp is older than 24 hours (-mtime +1), then

  3. Print the name of the thing we've found (-print).


The parentheses are there for precedence between the two sets of tests. They need to be escaped as they would otherwise be handled by the shell (as defining a sub-shell).



By default, find outputs the pathnames of the found files. This means that you'll get filenames prepended by ./ from the above command. If you don't want that, then you will have to call the basename utility for each found filename.



You can do that like this:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec basename {} ;


In comments you mention that you'd like to compress these files. For this, there is no need to call the basename utility. Just call gzip (or whatever compression utility you'd like to use) instead:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec gzip {} +


Depending on whether you'd like to do something further with these files, you may look for similar question on this site, e.g. Why is looping over find's output bad practice?



Also related:




  • Understanding the -exec option of `find`






share|improve this answer















Assuming that the implementation of find on your Unix has the -maxdepth predicate (it's non-standard, but often available), the following find command would do that:



find . -maxdepth 1 -type f -mtime +1


This would print the names of the regular files (i.e. not directories, sockets, named pipes etc.) whose modification timestamp was more than 24 hours ago to the terminal.



If -maxdepth can't be used, then consider



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -print


This means:




  1. If the current thing find is looking at is a directory (-type d), and

  2. If its name is not . (! -name .), i.e. it's a subdirectory, then


  3. Prune that directory from the search path of find (-prune). This stops find from even considering anything beneath subdirectories.


Otherwise (-o):




  1. If the thing is a regular file (-type f), and

  2. If its modification timestamp is older than 24 hours (-mtime +1), then

  3. Print the name of the thing we've found (-print).


The parentheses are there for precedence between the two sets of tests. They need to be escaped as they would otherwise be handled by the shell (as defining a sub-shell).



By default, find outputs the pathnames of the found files. This means that you'll get filenames prepended by ./ from the above command. If you don't want that, then you will have to call the basename utility for each found filename.



You can do that like this:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec basename {} ;


In comments you mention that you'd like to compress these files. For this, there is no need to call the basename utility. Just call gzip (or whatever compression utility you'd like to use) instead:



find . ( -type d ! -name . -prune ) -o -type f -mtime +1 -exec gzip {} +


Depending on whether you'd like to do something further with these files, you may look for similar question on this site, e.g. Why is looping over find's output bad practice?



Also related:




  • Understanding the -exec option of `find`







share|improve this answer














share|improve this answer



share|improve this answer








edited 15 hours ago

























answered 17 hours ago









KusalanandaKusalananda

136k17257425




136k17257425








  • 2





    Comments are not for extended discussion; this conversation has been moved to chat.

    – terdon♦
    15 hours ago











  • Is there any way using xargs to implement the same?

    – Anony
    14 hours ago











  • @Anony Not in any way that would help I think. Also, this comment section was archived in a chat. Do consider using it. Also note that I've asked multiple times for the actual command that you are using. I can't debug anything without seeing it. Do not post further comments in this thread, but do feel welcome to use the chat.

    – Kusalananda
    14 hours ago
















  • 2





    Comments are not for extended discussion; this conversation has been moved to chat.

    – terdon♦
    15 hours ago











  • Is there any way using xargs to implement the same?

    – Anony
    14 hours ago











  • @Anony Not in any way that would help I think. Also, this comment section was archived in a chat. Do consider using it. Also note that I've asked multiple times for the actual command that you are using. I can't debug anything without seeing it. Do not post further comments in this thread, but do feel welcome to use the chat.

    – Kusalananda
    14 hours ago










2




2





Comments are not for extended discussion; this conversation has been moved to chat.

– terdon♦
15 hours ago





Comments are not for extended discussion; this conversation has been moved to chat.

– terdon♦
15 hours ago













Is there any way using xargs to implement the same?

– Anony
14 hours ago





Is there any way using xargs to implement the same?

– Anony
14 hours ago













@Anony Not in any way that would help I think. Also, this comment section was archived in a chat. Do consider using it. Also note that I've asked multiple times for the actual command that you are using. I can't debug anything without seeing it. Do not post further comments in this thread, but do feel welcome to use the chat.

– Kusalananda
14 hours ago







@Anony Not in any way that would help I think. Also, this comment section was archived in a chat. Do consider using it. Also note that I've asked multiple times for the actual command that you are using. I can't debug anything without seeing it. Do not post further comments in this thread, but do feel welcome to use the chat.

– Kusalananda
14 hours ago




















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f506959%2fhow-can-i-get-files-using-find-command%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

數位音樂下載

Image
數位音樂下載 為非以「實體」方式來販賣音樂的相關產品，而使用數位格式如mp3、AAC等文件格式來進行銷售販賣的一种音乐产业形式。著名的數位音樂下載服務商有iTunes Store、RecoChoku、Google Play音乐和微软Zune等。数字音乐下载在二十一世纪初一度风靡全球， [1] [2] 使得传统唱片产业走向衰落，但其自身也在2010年代流媒体音乐服务如Apple Music、Spotify等的挤压下迅速失去市场份额。 [3] [4] 数字音乐下载有便于携带、传播迅速、制作简单成本低等优点，与流媒体音乐相比也能更好保障音乐人权益； [5] 但它同时很可能带来侵犯版权和滥用的情形， [6] 也给音乐产业带来了诸多不利影响。数字音乐下载为音乐人和乐迷提供了更加便捷直接的交流渠道，也一定程度上推动了网络音乐人的出现和独立音乐的迅速发展。 [7] 目录 1 历史 1.1 技术积淀（1987-2000） 1.2 出现与兴起（2000-2004） 1.3 唱片市场的颠覆者（2004-2007） 1.4 巅峰和衰落（2005-2013） 1.5 摇摇欲坠的现状与不可预知的明天（2014至今） 2 主要文件格式 2.1 PCM编码格式 2.1.1 WAV 2.1.2 APE 2.1.3 FLAC 2.2 苹果推出的无损文件格式 2.2.1 AIFF 2.2.2 ALAC 2.3 有损压缩格式 2.3.1 MP3 2.3.2 AAC 3 主要市场 3.1 iTunes Store 3.2 Google Play音乐商店 3.3 亚马逊音乐商店 3.4 部分其他音乐商店 4 影响与评价 4.1 对音乐产业的影响 4.2 对科技行业的影响 4.3 正面评价 4.4 负面评价 4.4.1 侵权问题 4.4.2 经营模式不明晰 4.4.3 不适应移动时代 4.5 文化现象 5 延伸阅读 6 参考资料 历史 苹果iTunes+iPod的软硬件搭配让数字音...
Read more

When can things happen in Etherscan, such as the picture below?

Image
2 I don't know why balance of the address is 0. when can this situation? etherscan balances share | improve this question asked yesterday Ru Hi Ru Hi 11 1 New contributor Ru Hi is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment  |  ...
Read more

格利澤436b

Image
格利泽436b 太陽系外行星 太陽系外行星列表 艺术家笔下的格利泽436b 母恆星 母恆星 Gliese 436 星座 獅子座 赤經 ( α ) 11 h  42 m  11.0941 s [1] 赤緯 ( δ ) +26° 42′ 23.652″ [1] 距離 33.4 ly (10.2 pc) 光譜類型 M2.5 V [1] 軌道參數 半长轴 ( a ) 0.0291±0.0004 [2] AU 軌道離心率 ( e ) 0.150±0.012 [2] 公轉週期 ( P ) 2.643904±0.000005 [3] d (0.00723849 y) 軌道傾角 ( i ) 85.8 +0.21 −0.25 [3] ° 角距 ( θ ) 2.794 mas 近星點時間 ( T 0 ) 2,451,551.716 ±0.01 JD 半振幅 ( K ) 18.68±0.8 m/s 物理性质 质量 ( m ) 22.2±1.0 [2] M ⊕ 半徑 ( r ) 4.327±0.183 [2] [4] R ⊕ 密度 ( ρ ) 1.51 g cm -3 表面重力 ( g ) 1.18 g 溫度 ( T ) 712±36 [2] K 發現 發現時間 2004 發現者 巴特勒、沃格特、 馬西 et al. 發現方法 徑向速度、凌日法 發現地點 美國加利福尼亞州 發表論文 出版 其他名稱 Ross 905 b, GJ 436 b, [5] LTT 13213 b, GCTP 2704.10 b, LHS 310, AC+27:28217 b, Vyssotsky 616 b, HIP 57087 b, GEN# +9.80120068 b, LP 319-75 b, G 121-7 b, LSPM J1142+2642 b, 1RXS J114211.9+264328 b, ASCC 683818 b, G 147-68 b, UCAC2 41198281 b, BP...
Read more