I am running a script through cron but keep getting this message in unix mail:
Subject: cron
Not a terminal
stty: : Not a typewriter
stty: : Not a typewriter
logout
The script appears to run successfully. Any ideas what this message is and how I can stop it? (1 Reply)
Hey Guys,
Ive got a script which when run from the command prompt works exactly as planned. However when this script is scheduled to run from the crontab (using the same user ID) it brings up a series of mmap errors...
+ /opt/cobol/bin/rebuild /cybtirl/data/file02 -k:4+32 -e -i -v
Error... (1 Reply)
I am using the following cron entry to run a cron job every 4 hours and
it is rejecting it:
0 */4 * * * /home/location/scriptname
When I put this entry in cron is errors with: 0481-079 reached a symbol that is not expected.
This is an AIX 5.3 system
Any ideas?
Thanks (4 Replies)
I am using the following cron entry to run a cron job every 4 hours and
it is rejecting it:
0 */4 * * * /home/location/scriptname
When I put this entry in cron is errors with: 0481-079 reached a symbol that is not expected.
This is an AIX 5.3 system
Any ideas?
Thanks (6 Replies)
Hi All,
please help me out with this problem.
While running my mail_out_original.ksh in CRT window, it disconnects from the server saying not connected
Here is my code : (please see the attachment)
____________________________________________________________
#!/bin/ksh
## Load... (1 Reply)
HI
am having a script file which is ok if i run from the server manually
like
<root@hostname:/space/canvas/home/lbs/current/internalcdrbackup/LES_CDR_Configuration/0/MSISDNcdrCount > /space/canvas/home/lbs/current/internalcdrbackup/LES_CDR_Configuration/0/MSISDNcdrCount.txt
the... (2 Replies)
I am attempting to run a cron job, however, I receive this cron output error:
Error: of parameter : xxxxx does not make a valid output file.
What causes this? (4 Replies)
Hi all,
I am brand new in linux and i have a cron lon error which i am trying to locate if anyone has any ideas that would be really appreciated
################### Logwatch 7.3.6 (05/19/07) ####################
Processing Initiated: Thu Nov 10 06:25:26 2011
Date Range... (0 Replies)
Hi all,
I am brand new in linux and not sure where to post this i posted it also on debian but i think this place would have been better. I have a cron log error which i am trying to locate if anyone has any ideas that would be really appreciated
################### Logwatch 7.3.6... (3 Replies)
Hi all, I write from 'Italy (sorry for my english)
I have a joomla site, some days I get an error with cronjobs
I do not know how to fix it (I'm not an expert)
I kindly ask you to help you who are more experienced
the error is this:
Status: 403 Forbidden
Set-Cookie: =... (1 Reply)
Discussion started by: arredoannunci
1 Replies
LEARN ABOUT LINUX
git-shell
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
SEE ALSO ssh(1), git-daemon(1), contrib/git-shell-commands/README
GIT
Part of the git(1) suite
Git 1.8.5.3 01/14/2014 GIT-SHELL(1)