Expect script not executing via cron Post: 302977887

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

expect script in cron

I wrote a script using 'expect' tool to change the password of my login id, every fortnight. And I had put it as a cron job. The cron job is throwing an error ld.so.1: /usr/local/bin/expect: fatal: libtcl8.3.so: open failed: No such file or directory The environment variables are set...

2. HP-UX

executing shell script from the cron

This isn't the usual problem that a shell script runs from the command line and not the cron. It's a little different. Among other things, the shell scrip executes my .profile to set a bunch of variables. It then does an env to ensure that it ran OK. There are echos in the shell script and...

3. Shell Programming and Scripting

Using expect script with AIX's SMIT in cron

My searches turned up nothing relevant, so I apologize if this has already been looked at. I am trying to run an expect script from a Solaris machine, that ssh's into an AIX machine, and interacts with a SMIT created menu system that runs a few backups for me. The expect script runs fine when...

4. Shell Programming and Scripting

Executing expect script giving message as bad interpreter: Permission denied

Hi Gurus, I am new to scripting and needs your help in expect script used for telnet. I wrote a simple script as #!/usr/bin/expect-5.43 -f spawn telnet localhost 2233 expect "password:" send "secret\r" send "i data.cnbc.com\r" send "exit\r" expect eof When I am trying to execute...

5. Shell Programming and Scripting

Problem with executing a shell script through the cron

Hi, I have a shell script as below: ORACLE_HOME=/usr/local/opt/oracle/product/dev export ORACLE_HOME PATH=$PATH:$ORACLE_HOME/bin:/usr/bin export PATH OUTFILE=/export/home/`basename $0`.out export OUTFILE export IDEN df -k . | tail -1 | read a b c d e f echo $a >> $OUTFILE echo $b...

6. Shell Programming and Scripting

Executing a script from CRON behaves differently than terminal

Hi have a script which transferers from Microsoft server to Linux box. The scripts(ksh) is on Linux box. If I run script from terminal, it transfers files to directory. Where as If I run script from CRON. It does not. Here is the log of both: Terminal execution log:...

7. UNIX for Dummies Questions & Answers

Cron shell script not executing diskutil command

I'm trying to learn how to use cron for repetative tasks. I have an external disk that needs to be unmounted and remounted every hour due to some problems that a backup utility (specifically, TimeMachine) is having repeatedly accessing the device. I've created a shell script that will find the...

8. Shell Programming and Scripting

Script not executing using cron

Hi, I created a script which connects to database and update a table. This script is running fine when i run it manually but when i am trying to execute it scheduling in crontab.script is executing but Data is not getting updated. below is my script sqlplus test/##### >> test_feed.log <<!...

9. Shell Programming and Scripting

Expect Script not running from cron. Full Paths used

My cron file. Copied $PATH # Minute Hour Day of Month Month Day of Week Command SHELL=/bin/ksh PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/perl/lib:/perl/lib/lib/perl5:/perl/scripts:.:/perl/lib/local:/home/popeye:/temp 0...

10. AIX

Script is not executing as expected when I schedule it in cron

Hi, I have a shell script which fetches the MRP status and the LAG status. When I execute it manually like, sh <script_name>, it fetches the output as expected, but when I schedule through crontab, it's not working as expected. Any help would be really appreciated. Here is the code...

LEARN ABOUT CENTOS

systemd-run

SYSTEMD-RUN(1)							    systemd-run 						    SYSTEMD-RUN(1)

NAME

       systemd-run - Run programs in transient scope or service units

SYNOPSIS

       systemd-run [OPTIONS...] COMMAND [ARGS...]

DESCRIPTION

       systemd-run may be used to create and start a transient .service or a .scope unit and run the specified COMMAND in it.

       If a command is run as transient service unit, it will be started and managed by the service manager like any other service, and thus show
       up in the output of systemctl list-units like any other unit. It will run in a clean and detached execution environment.  systemd-run will
       start the service asynchronously in the background and immediately return.

       If a command is run as transient scope unit, it will be started directly by systemd-run and thus inherit the execution environment of the
       caller. It is however managed by the service manager similar to normal services, and will also show up in the output of systemctl
       list-units. Execution in this case is synchronous, and execution will return only when the command finishes.

OPTIONS

       The following options are understood:

       -h, --help
	   Prints a short help text and exits.

       --version
	   Prints a short version string and exits.

       --user
	   Talk to the service manager of the calling user, rather than the service manager of the system.

       --system
	   Talk to the service manager of the system. This is the implied default.

       --scope
	   Create a transient .scope unit instead of the default transient .service unit.

       --unit=
	   Use this unit name instead of an automatically generated one.

       --description=
	   Provide description for the unit. If not specified, the command itself will be used as a description. See Description= in
	   systemd.unit(5).

       --slice=
	   Make the new .service or .scope unit part of the specified slice, instead of the system.slice.

       --remain-after-exit
	   After the service's process has terminated, keep the service around until it is explicitly stopped. This is useful to collect runtime
	   information about the service after it finished running. Also see RemainAfterExit= in systemd.service(5).

       --send-sighup
	   When terminating the scope unit, send a SIGHUP immediately after SIGTERM. This is useful to indicate to shells and shell-like processes
	   that the connection has been severed. Also see SendSIGHUP= in systemd.kill(5).

       All command-line arguments after the first non-option argument become part of the commandline of the launched process. If a command is run
       as service unit, its first argument needs to be an absolute binary path.

EXIT STATUS

       On success, 0 is returned, a non-zero failure code otherwise.

EXAMPLE

       The following command will log the environment variables provided by systemd to services:

	   # systemd-run env
	   Running as unit run-19945.service.
	   # journalctl -u run-19945.service
	   Sep 08 07:37:21 bupkis systemd[1]: Starting /usr/bin/env...
	   Sep 08 07:37:21 bupkis systemd[1]: Started /usr/bin/env.
	   Sep 08 07:37:21 bupkis env[19948]: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
	   Sep 08 07:37:21 bupkis env[19948]: LANG=en_US.UTF-8
	   Sep 08 07:37:21 bupkis env[19948]: BOOT_IMAGE=/vmlinuz-3.11.0-0.rc5.git6.2.fc20.x86_64

SEE ALSO

       systemd(1), systemctl(1), systemd.unit(5), systemd.service(5), systemd.scope(5), systemd.slice(5).

systemd 208															    SYSTEMD-RUN(1)

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

expect script in cron

Discussion started by: Deepa

2. HP-UX

executing shell script from the cron

Discussion started by: abNORMal

3. Shell Programming and Scripting

Using expect script with AIX's SMIT in cron

Discussion started by: Mariognarly

4. Shell Programming and Scripting

Executing expect script giving message as bad interpreter: Permission denied

Discussion started by: niks_yv