The cron job was set to 06 am but the file wasn't copied again and cronlog.err says this:
I've checked yesterday on source server (SunOS) at 23:30 and after 01:00 of today and the file logfile.2019-03-06 hasn't been created at that time.
But now checking the source server appears like the logfile was created yesterday at 22:00 but like I say above after 23:00 the file wasn't there.
So I think the file on SunOS appears like is created yesterday but probably was created after 06:00 of today, I don't know. It confuses me since the date appears March 6 at 22:00.
Is there a way to check on SunOS really when was created on /path/to/LogFiles/ directory?
i have a script that uses an ant build.xml and its targets to pull a project from a cvs server, attempt to build the project, and then email me the results. When I run the script (either @ CLI or as a cron job) while I am logged in, everything works fine. However, if the script is set up to run... (5 Replies)
I have the following crontab entry to run a shell script for every 30 minutes of every day:
30 * * * * $HOME/main.sh > $HOME/main.log 2>$HOME/error.log
after I created the crontab file I have also done:
$crontab my_crontab
I also check to make sure it exists, by using the following... (11 Replies)
hi guys,
i have a problem.
a week ago i made a successful crontab that execute bash scripting daily, it worked well
but now, it doesn't work at all, in the mail i have:
"
/home/jimmy/cha/scripts/cekpderr
produced the following output:
lagi jalan
/home/jimmy/cha/scripts/cekpderr:... (6 Replies)
I have a script running in the crontab that gets data from a database every hour. Now I would like to execute a fortran routine to process the data in some way, after getting it and saving it locally.
I have added the following commands to my script:
set convert =... (1 Reply)
I wrote a script to shutdown the oracle database. The script works fine when I manually run the script. However, when i schedule a job, i get the following error.
Shutting Down cmismart ....................
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4... (6 Replies)
Hi all,
I really need your help ASAP on this. Below is the description of my problem and a sketch of Autosys
Job Activity Console
++++++++++++++++++++++++++++++++
File View Options
+++++++++++++++++++++++++++++++
Job Name Description Status Command Machine... (1 Reply)
The .profile file should be read when the user logs in. So, there should be no need to execute .profile file again in a cron job (since the cron job is run after the user logs in). Doesn't the cron require login from the user. Then, from where does the cron execute? Please help!! (1 Reply)
Hi,
I am trying to execute a script (for once) during the booting time in Ubuntu system. However, the result is only showing the strings without without the variables.
Here is the script:
MgrIp=$(ec2-describe-instances --filter tag:Name=Mgr --filter instance-state-name=running | egrep... (4 Replies)
Dear *nix users.
I'm on Mac OS 10.6 / Terminal and try to use crontab to schedule two scripts every 30 minutes and every 41 minutes.
I followed the man instructions and created / installed a crontab file for the current user:crontab -e
with the following content
*/30 * * * *... (4 Replies)
Dear All,
My server is running crontabs of 4 different users.
I want to develop a script that whenever a particular change occurs in a crontab , it is detected and the particular change is noted into a file.
Kindly let me know of suggestions on how it can be achieved.
My algo would be:
... (1 Reply)
Discussion started by: Junaid Subhani
1 Replies
LEARN ABOUT HPUX
chroot
chroot(1M)chroot(1M)NAME
chroot - change root directory for a command
SYNOPSIS
newroot command
DESCRIPTION
The command executes command relative to the newroot. The meaning of any initial slashes in path names is changed for command and any of
its children to newroot. Furthermore, the initial working directory is newroot.
Note that command suffixes that affect input or output for the command use the original root, not the new root. For example, the command:
locates file relative to the original root, not the new one.
The command variable includes both the command name and any arguments.
The new root path name is always relative to the current root. Even if a is currently in effect, the newroot argument is relative to the
current root of the running process.
This command is restricted to users with appropriate privileges.
EXTERNAL INFLUENCES
International Code Set Support
Single- and multibyte character code sets are supported.
WARNINGS
command cannot be in a shell script.
Exercise extreme caution when referring to special files in the new root file system.
does not search the environment variable for the location of command, so the absolute path name of command must be given.
When using to establish a new environment, all absolute path name references to the file system are lost, rendering shared libraries inac-
cessible. If continued access to shared libraries is needed for correct operation, the shared libraries and the dynamic loader be copied
into the new root environment.
SEE ALSO chdir(2), chroot(2).
STANDARDS CONFORMANCE chroot(1M)