How to read .sh_history from thousand of users?
The logic applies to many other objectives.
And how to read .sh_history of each user from /home/ filesystem? What if there are thousand of them?
command-line scripts
asked Sep 30 '18 at 16:54
Igor MV
11
add a comment |
The logic applies to many other objectives.
And how to read .sh_history of each user from /home/ filesystem? What if there are thousand of them?
command-line scripts
asked Sep 30 '18 at 16:54
Igor MV
11
add a comment |
The logic applies to many other objectives.
And how to read .sh_history of each user from /home/ filesystem? What if there are thousand of them?
command-line scripts
asked Sep 30 '18 at 16:54
Igor MV
11
The logic applies to many other objectives.
And how to read .sh_history of each user from /home/ filesystem? What if there are thousand of them?
command-line scripts
command-line scripts
asked Sep 30 '18 at 16:54
Igor MV
11
asked Sep 30 '18 at 16:54
Igor MV
11
asked Sep 30 '18 at 16:54
Igor MV
11
asked Sep 30 '18 at 16:54
Igor MV
11
asked Sep 30 '18 at 16:54
Igor MV
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This is Hard. You will have to interpret each user's ~/.bashrc, and all the "Startup Files" for each and every shell to see what "the history file" really is.
For example, mine sets my history file to ~/.history/history.$$, and I currently have 1372 .history files.
My ~/.bashrc fragment:
[[ -d ~/.history ]] || mkdir --mode=0700 ~/.history
[[ -d ~/.history ]] && chmod 0700 ~/.history
HISTFILE=~/.history/history.$$
# close any old history file by zeroing HISTFILESIZE
HISTFILESIZE=0
# then set HISTFILESIZE to a large value
HISTFILESIZE=4096
HISTSIZE=4096
Other users may do other things, may call their .history files something else, use other shells, ...
answered Sep 30 '18 at 20:09
waltinator
21.9k74169
So you have a separate history file for each shell invocation? Interesting idea. I cannot think of a usecase for me but I'm pretty sure you have one.
– PerlDuck
Dec 2 '18 at 12:24
@PerlDuck From deleted self-answer posted by OP it is worth mentioning this question is about Korn Shell (#!/bin/ksh) not Bash Shell (#!/bin/bash). Korn Shell has different history file issues.
– WinEunuuchs2Unix
Dec 2 '18 at 23:33
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1079772%2fhow-to-read-sh-history-from-thousand-of-users%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
This is Hard. You will have to interpret each user's ~/.bashrc, and all the "Startup Files" for each and every shell to see what "the history file" really is.
For example, mine sets my history file to ~/.history/history.$$, and I currently have 1372 .history files.
My ~/.bashrc fragment:
[[ -d ~/.history ]] || mkdir --mode=0700 ~/.history
[[ -d ~/.history ]] && chmod 0700 ~/.history
HISTFILE=~/.history/history.$$
# close any old history file by zeroing HISTFILESIZE
HISTFILESIZE=0
# then set HISTFILESIZE to a large value
HISTFILESIZE=4096
HISTSIZE=4096
Other users may do other things, may call their .history files something else, use other shells, ...
answered Sep 30 '18 at 20:09
waltinator
21.9k74169
So you have a separate history file for each shell invocation? Interesting idea. I cannot think of a usecase for me but I'm pretty sure you have one.
– PerlDuck
Dec 2 '18 at 12:24
@PerlDuck From deleted self-answer posted by OP it is worth mentioning this question is about Korn Shell (#!/bin/ksh) not Bash Shell (#!/bin/bash). Korn Shell has different history file issues.
– WinEunuuchs2Unix
Dec 2 '18 at 23:33
add a comment |
This is Hard. You will have to interpret each user's ~/.bashrc, and all the "Startup Files" for each and every shell to see what "the history file" really is.
For example, mine sets my history file to ~/.history/history.$$, and I currently have 1372 .history files.
My ~/.bashrc fragment:
[[ -d ~/.history ]] || mkdir --mode=0700 ~/.history
[[ -d ~/.history ]] && chmod 0700 ~/.history
HISTFILE=~/.history/history.$$
# close any old history file by zeroing HISTFILESIZE
HISTFILESIZE=0
# then set HISTFILESIZE to a large value
HISTFILESIZE=4096
HISTSIZE=4096
Other users may do other things, may call their .history files something else, use other shells, ...
answered Sep 30 '18 at 20:09
waltinator
21.9k74169
So you have a separate history file for each shell invocation? Interesting idea. I cannot think of a usecase for me but I'm pretty sure you have one.
– PerlDuck
Dec 2 '18 at 12:24
@PerlDuck From deleted self-answer posted by OP it is worth mentioning this question is about Korn Shell (#!/bin/ksh) not Bash Shell (#!/bin/bash). Korn Shell has different history file issues.
– WinEunuuchs2Unix
Dec 2 '18 at 23:33
add a comment |
This is Hard. You will have to interpret each user's ~/.bashrc, and all the "Startup Files" for each and every shell to see what "the history file" really is.
For example, mine sets my history file to ~/.history/history.$$, and I currently have 1372 .history files.
My ~/.bashrc fragment:
[[ -d ~/.history ]] || mkdir --mode=0700 ~/.history
[[ -d ~/.history ]] && chmod 0700 ~/.history
HISTFILE=~/.history/history.$$
# close any old history file by zeroing HISTFILESIZE
HISTFILESIZE=0
# then set HISTFILESIZE to a large value
HISTFILESIZE=4096
HISTSIZE=4096
Other users may do other things, may call their .history files something else, use other shells, ...
answered Sep 30 '18 at 20:09
waltinator
21.9k74169
This is Hard. You will have to interpret each user's ~/.bashrc, and all the "Startup Files" for each and every shell to see what "the history file" really is.
For example, mine sets my history file to ~/.history/history.$$, and I currently have 1372 .history files.
My ~/.bashrc fragment:
[[ -d ~/.history ]] || mkdir --mode=0700 ~/.history
[[ -d ~/.history ]] && chmod 0700 ~/.history
HISTFILE=~/.history/history.$$
# close any old history file by zeroing HISTFILESIZE
HISTFILESIZE=0
# then set HISTFILESIZE to a large value
HISTFILESIZE=4096
HISTSIZE=4096
Other users may do other things, may call their .history files something else, use other shells, ...
answered Sep 30 '18 at 20:09
waltinator
21.9k74169
edited Sep 30 '18 at 23:44
answered Sep 30 '18 at 20:09
waltinator
21.9k74169
answered Sep 30 '18 at 20:09
waltinator
21.9k74169
answered Sep 30 '18 at 20:09
waltinator
21.9k74169
21.9k74169
So you have a separate history file for each shell invocation? Interesting idea. I cannot think of a usecase for me but I'm pretty sure you have one.
– PerlDuck
Dec 2 '18 at 12:24
@PerlDuck From deleted self-answer posted by OP it is worth mentioning this question is about Korn Shell (#!/bin/ksh) not Bash Shell (#!/bin/bash). Korn Shell has different history file issues.
– WinEunuuchs2Unix
Dec 2 '18 at 23:33
add a comment |
So you have a separate history file for each shell invocation? Interesting idea. I cannot think of a usecase for me but I'm pretty sure you have one.
– PerlDuck
Dec 2 '18 at 12:24
@PerlDuck From deleted self-answer posted by OP it is worth mentioning this question is about Korn Shell (#!/bin/ksh) not Bash Shell (#!/bin/bash). Korn Shell has different history file issues.
– WinEunuuchs2Unix
Dec 2 '18 at 23:33
So you have a separate history file for each shell invocation? Interesting idea. I cannot think of a usecase for me but I'm pretty sure you have one.
– PerlDuck
Dec 2 '18 at 12:24
So you have a separate history file for each shell invocation? Interesting idea. I cannot think of a usecase for me but I'm pretty sure you have one.
– PerlDuck
Dec 2 '18 at 12:24
@PerlDuck From deleted self-answer posted by OP it is worth mentioning this question is about Korn Shell (
#!/bin/ksh) not Bash Shell (#!/bin/bash). Korn Shell has different history file issues.– WinEunuuchs2Unix
Dec 2 '18 at 23:33
@PerlDuck From deleted self-answer posted by OP it is worth mentioning this question is about Korn Shell (
#!/bin/ksh) not Bash Shell (#!/bin/bash). Korn Shell has different history file issues.– WinEunuuchs2Unix
Dec 2 '18 at 23:33
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1079772%2fhow-to-read-sh-history-from-thousand-of-users%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
