Having a problem on AIX 4.3.3 with the following error when more than 2 users try and sign onto the server.
3004-312 All available login sessions are in use.
???? (1 Reply)
Can I do it like this?
if (strcmp(argv, "history")==0)
{
argv = "10";
execvp(argc,argv);
}
actually, it doesn't work,
How can I modify it?
Thanks (17 Replies)
Like the topic says, does anyone know if it is possible to check to see when an FTP only user has logged in? Because the shell is /bin/false and they are only using FTP to access the system doing a "finger" or "last" it says they have never logged in.
Is there a way to see when ftp users log in... (1 Reply)
I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Hi,
I have a unix server and I am concerned about the security on that server.
I would like to be able to write a script that records all the commands that were typed at the command prompt before the user calls the 'history -c' command and deletes all the history.
I was thinking about firing or... (7 Replies)
Besides 'who am i' and 'tty' what commands could be used to determine if a session is interactive as compared to a web process or cron process. Any command should work with the common unix variants. (3 Replies)
I'm looking for a way to track commands that are run as root after a user runs sudo su - root. I have a profile set up for root that will track the commands by userid but if we change the shell it only stores it in that shells history file. (2 Replies)
I use plink.exe to automate remote commands that return data to Windows machines. This works well on newer servers running Red Hat since the commands were developed for bash and the designated user's login shell is bash. I need to also support older servers which are running Solaris 10 but the... (5 Replies)
Discussion started by: randman1
5 Replies
LEARN ABOUT DEBIAN
devel::repl::plugin::readlinehistory
Devel::REPL::Plugin::ReadLineHistory(3pm) User Contributed Perl Documentation Devel::REPL::Plugin::ReadLineHistory(3pm)NAME
Devel::REPL::Plugin::ReadLineHistory - Integrate history with the facilities provided by Term::ReadLine
DESCRIPTION
This plugin enables loading and saving command line history from a file as well has history expansion of previous commands using the
!-syntax a la bash.
By default, history expansion is enabled with this plugin when using Term::ReadLine::Gnu. That means that "loose" '!' characters will be
treated as history events which may not be what you wish.
To avoid this, you need to quote the '!' with '':
my $var = "foo!";
or place the arguments in single quotes---but enable the "Term::ReadLine" attribute "history_quotes_inhibit_expansion":
$_REPL->term->Attribs->{history_quotes_inhibit_expansion} = 1;
my $var = 'foo!';
and to disable history expansion from GNU readline/history do
$_REPL->term->Attribs->{do_expand} = 0;
CONFLICTS
Note that Term::ReadLine::Perl does not support a history expansion method. In that case, you may wish to use the Devel::REPL History
plugin which provides similar functions. Work is underway to make use of either History or ReadLineHistory consistent for expansion with
either the Term::ReadLine::Gnu support or Term::ReadLine::Perl.
perl v5.14.2 2010-06-13 Devel::REPL::Plugin::ReadLineHistory(3pm)