Hi there, this is part of my script:
/usr/bin/cd /u01/oradata
/usr/bin/cp `/bin/ls -1 . |grep -v "^DIMStemp01.dbf$" | grep -v "^DIMSts01.dbf$"|grep -v "^DIMStects01.dbf$"` /backup
It's working fine when I manually run on telnet session.
/bin/ls -1 . -- to list all the files inside... (2 Replies)
Hi,
This script is working successfully when i executed from shell prompt, but the same script scheduled in crontab its not deleting the files,
#! /bin/bash
DAY_1=`(date --date='4 months ago' '+%Y-%m')`
log=/tmp/cleant
adir=/u01/app/oracle/admin/talon/adump... (4 Replies)
I have the following expect script sitting on a Linux box.
===
#!/usr/bin/expect -f
#
# backup.expect
#
# Expect script to backup a firewall via a SSH session
#
#
set firewall
set username
set password
set prompt
set filename
match_max 50000
spawn ssh -l... (2 Replies)
I have made a shell script(/bin/sh) that starts a perl script (that I haven't made my self) that's starts a ssh session. The ssh session uses a private/public key to login so no password is needed. The Perl script works perfect.
But when I put it in a cronjob (crontab) the ssh connection asks... (6 Replies)
This is the crontab it is supossed to be running everyday but it didnt
5 0 * * * /export/app/CO/opge/scr/Informe_parametros_colombia.ksh >/dev/null 2>&1
Inside the above script connects to a database and extract data to a flat file, manually i run the script at about 2 a.m. and Works OK,... (6 Replies)
Hi All,
I am testing expect script in command prompt without issue, but in crontab it is not working, i check the output error as below:
#cat /var/log/testexp.log
spawn minicom -C /var/log/minicom1.log
No cursor motion capability (cm)
AT+COPS=?
I am new in scripting, together... (1 Reply)
Hi all,
I'm working to a script with /bin/bash shebang.
The script works perfectly if I run from command line.
The script runs under a non root user and inside the commands are set with sudo command in a such a way they can be run under root, for example (first rows of the script):... (5 Replies)
Hi,
I have written one script which is connecting to the the database and generating one CSV, it is running fine when i ran it manually though it is throwing any warning but CSV is generating and working fine but same script when i have configured in crontab not working and giving error, kindly... (6 Replies)
Hi,
I have written one script which is connecting to the the database and generating one CSV, it is running fine when i ran it manually though it is throwing any warning but CSV is generating and working fine but same script when i have configured in crontab not working and giving error, kindly... (1 Reply)
I am Not sure why following script is not capturing the counts only when using crontab !! when I run it fromt he command line it is fine ! what is missing here !
#!/usr/bin/ksh
host=`uname -n`
tdate=`date`
userid='dbid/password'
totalevents=`sqlplus -s $userid << -
set timing off
... (1 Reply)
Discussion started by: mrn6430
1 Replies
LEARN ABOUT XFREE86
pty
PTY(4) BSD Kernel Interfaces Manual PTY(4)NAME
pty -- BSD-style compatibility pseudo-terminal driver
SYNOPSIS
device pty
DESCRIPTION
The pty driver provides support for the traditional BSD naming scheme that was used for accessing pseudo-terminals. When the device
/dev/ptyXX is being opened, a new terminal shall be created with the pts(4) driver. A device node for this terminal shall be created, which
has the name /dev/ttyXX.
New code should not try to allocate pseudo-terminals using this interface. It is only provided for compatibility with older C libraries that
tried to open such devices when posix_openpt(2) was being called.
FILES
The BSD-style compatibility pseudo-terminal driver uses the following device names:
/dev/pty[l-sL-S][0-9a-v] Pseudo-terminal master devices.
/dev/tty[l-sL-S][0-9a-v] Pseudo-terminal slave devices.
DIAGNOSTICS
None.
SEE ALSO posix_openpt(2), pts(4), tty(4)HISTORY
A pseudo-terminal driver appeared in 4.2BSD.
BUGS
Unlike previous implementations, the master slave device nodes are destroyed when the PTY becomes unused. A call to stat(2) on a nonexistent
master device will already cause a new master device node to be created. The master device can only be destroyed by opening and closing it.
The pty driver cannot be unloaded, because it cannot determine if it is being used.
BSD August 20, 2008 BSD
08-06-2012
