Sponsored Content
Full Discussion: HP-UX history settings
Operating Systems HP-UX HP-UX history settings Post 302581818 by kinetik on Thursday 15th of December 2011 01:51:22 AM
Old 12-15-2011
Quote:
Originally Posted by vbe
This is another case...
In history files, you would expect to see all commands typed by the user if in a shellscript ther are many programs-commands called, since the user did not type them on the keyboard, very little chance will you have to see them in $HISTFILE...
Anything cron or other scheduler have their own log facilities that need to be configured adequatly to suit your request, in other words HISTFILE is set for a interactive shell only( logging the STDIN activity...)... This explains why you see nothing...

Which brings me to the other thing I neglected to mention (sorry, as it turns out I left out quite a lot of detail originally).
The automated system uses only Java libraries or plink.exe to connect from a Windows client machine. I know for a fact both the commands configured to run over the Java libs and plink.exe show up fine in the history.

EDIT: Scratch that, seems commands run over plink.exe do not show up... The plot thickens.

---------- Post updated 12-15-11 at 08:51 AM ---------- Previous update was 12-14-11 at 01:19 PM ----------

Quick update regarding this:


Checked, double-checked and checked again that any commands using Java libs show up in the history files. I'm not sure if every single command will show up, but I fully expect at least one instance of a command to show up at least once as the commands are all run every 10 minutes or so.

The commands using plink.exe are a bit trickier as they do not show up for some reason. I'm not sure how I'd go about running plink in such a way to make the O/S treat the session as a normal user SSH session (thereby dumping the commands ni the history files as well), but regardless, I'm reasonably sure the commands we run using plink are fine.
The only times we would use plink is if we connect to the HP-UX O/S by means of custom Python scripts and, since the bulk of these scripts were written by me and reside in a central location, I'm sure the command they claim was run would not have been kicked off by this.


At this point I must add that it turns out there's not just one automated system that connects to this server. It also turns out that the O/S account isn't exclusively used only by this one automated system...

I'll update again if anything worthwhile pops up. Thanks again for the help so far with this guys.

Last edited by kinetik; 12-14-2011 at 07:26 AM..
 

8 More Discussions You Might Find Interesting

1. Solaris

Duplex Settings

Hi All I've been having a lot of errors logged on the Cisco Catalyst (4000 series) which one of my Solaris servers is patched into. I have a feeling they are duplex related, but I'm a bit stuck as to how to confirm that. How do I: 1. Check the duplex settings on my eri0 card? 2. Set the... (3 Replies)
Discussion started by: saabir
3 Replies

2. UNIX for Dummies Questions & Answers

Network settings

Total newbie here!! How do I view and alter network settings (ip address, subnet mask and default gateway) in UNIX? Thanks in advance.. (3 Replies)
Discussion started by: ZappaDub
3 Replies

3. Linux

Ip settings

Hi, How to set ip address in linux. Regards, Guguli (1 Reply)
Discussion started by: guguli
1 Replies

4. UNIX for Dummies Questions & Answers

How to review the history and the commands that has been done in this history?

Hello every body, Kindly inform me How Do i find out the time I executed a command previously on UNIX Solaris?? To be more specific and more clear about what i want to know is that I want a command the enables me to know the history and which command i run at this history/time. FYI I used... (5 Replies)
Discussion started by: ahmedamer12
5 Replies

5. UNIX for Advanced & Expert Users

History to Another file [local user history , but root access]

Hi all, My need is : 1. To know who , when , which command used. 2. Local user should not delete this information. I mean , with an example , i can say i have a user user1 i need to give all the following permissions to user1, : a. A specific directory other than his home... (3 Replies)
Discussion started by: linuxadmin
3 Replies

6. UNIX for Dummies Questions & Answers

The history command: See other users command history

Can anyone tell this: If two users are logged into the same server from different locations. Is there a way to see the history command of the other user? I tried the history command, but it is showing me only the commands I used. Thanks in advance for your help. Iamnew2solaris (1 Reply)
Discussion started by: iamnew2solaris
1 Replies

7. UNIX for Dummies Questions & Answers

History to Another file [local user history , but root access]

Hi all, My need is : 1. To know who , when , which command used. 2. Local user should not delete this information. I mean , with an example , i can say i have a user user1 i need to give all the following permissions to user1, : a. A specific directory other than his home... (1 Reply)
Discussion started by: sriky86
1 Replies

8. What is on Your Mind?

The Great History of UNIX (1969-1999) | 30 Years of UNIX History | YouTube Video

I am pleased to announce this new video in 1080 HD for UNIX lovers honoring thirty years of UNIX history spanning from 1969 to 1999 presented in 150 seconds (two and a half minutes) in 1080 HD, celebrating the 50th anniversary of UNIX. The Great History of UNIX (1969-1999) | 30 Years of UNIX... (8 Replies)
Discussion started by: Neo
8 Replies
GIT-SHELL(1)                                                        Git Manual                                                        GIT-SHELL(1)

NAME
git-shell - Restricted login shell for Git-only SSH access SYNOPSIS
chsh -s $(command -v git-shell) <user> git clone <user>@localhost:/path/to/repo.git ssh <user>@localhost DESCRIPTION
This is a login shell for SSH accounts to provide restricted Git access. It permits execution only of server-side Git commands implementing the pull/push functionality, plus custom commands present in a subdirectory named git-shell-commands in the user's home directory. COMMANDS
git shell accepts the following commands after the -c option: git receive-pack <argument>, git upload-pack <argument>, git upload-archive <argument> Call the corresponding server-side command to support the client's git push, git fetch, or git archive --remote request. cvs server Imitate a CVS server. See git-cvsserver(1). If a ~/git-shell-commands directory is present, git shell will also handle other, custom commands by running "git-shell-commands/<command> <arguments>" from the user's home directory. INTERACTIVE USE
By default, the commands above can be executed only with the -c option; the shell is not interactive. If a ~/git-shell-commands directory is present, git shell can also be run interactively (with no arguments). If a help command is present in the git-shell-commands directory, it is run to provide the user with an overview of allowed actions. Then a "git> " prompt is presented at which one can enter any of the commands from the git-shell-commands directory, or exit to close the connection. Generally this mode is used as an administrative interface to allow users to list repositories they have access to, create, delete, or rename repositories, or change repository descriptions and permissions. If a no-interactive-login command exists, then it is run and the interactive shell is aborted. EXAMPLE
To disable interactive logins, displaying a greeting instead: $ chsh -s /usr/bin/git-shell $ mkdir $HOME/git-shell-commands $ cat >$HOME/git-shell-commands/no-interactive-login <<EOF #!/bin/sh printf '%s ' "Hi $USER! You've successfully authenticated, but I do not" printf '%s ' "provide interactive shell access." exit 128 EOF $ chmod +x $HOME/git-shell-commands/no-interactive-login To enable git-cvsserver access (which should generally have the no-interactive-login example above as a prerequisite, as creating the git-shell-commands directory allows interactive logins): $ cat >$HOME/git-shell-commands/cvs <<EOF if ! test $# = 1 && test "$1" = "server" then echo >&2 "git-cvsserver only handles "server"" exit 1 fi exec git cvsserver server EOF $ chmod +x $HOME/git-shell-commands/cvs SEE ALSO
ssh(1), git-daemon(1), contrib/git-shell-commands/README GIT
Part of the git(1) suite Git 2.17.1 10/05/2018 GIT-SHELL(1)
All times are GMT -4. The time now is 03:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy