11-17-2010
Maybe the service command can't found, try to use /sbin/service ..
If it works, you need to add PATH env variable in cron job.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I'm puzzled by this one. I hope you can explain it to me.
I have a ksh shell script that gzips a file among other things. This works perfectly fine when the script is manually run through a shell. However, when the same script is run through cron, it does everything correctly, but it will... (2 Replies)
Discussion started by: hbau419
2 Replies
2. Shell Programming and Scripting
Hello expert,
What I want is to determine whether the script is called from CRON or it is executed interactively?
I tried the following but no luck:
#!/bin/ksh
cronID=`pgrep -x cron`
GPID=`ps -ef -o ppid,pid | grep " $PPID$" | awk '{print $1}'`
if ; then
echo I am being run... (15 Replies)
Discussion started by: wes_brooks
15 Replies
3. AIX
how to stop perl service on AIX? how to find if per service runing? (4 Replies)
Discussion started by: rainbow_bean
4 Replies
4. Solaris
Hi,
I am working with a company where some times i need to start/stop cron jobs on need basis.
I have one option to kill cron daemon.Is it right?
Please correct me.
Waiting for your reply.
Thanks in advance.. (2 Replies)
Discussion started by: varaprasadu
2 Replies
5. Shell Programming and Scripting
Hello,
I have the following script which works fine when ran from the command line:
#!/apps/python/2.3.4/bin/python
import os
import sys
import time
user = os.getenv("USER")
string = time.strftime("%m%d%y0000 " + user, time.gmtime())
However, when I have this run by crontab, I... (4 Replies)
Discussion started by: cooldude
4 Replies
6. AIX
As topic, assume we have a service called "blahservice"
and we can start it by:
startsrc -s blahservice
what is the best practice to run such command when system start?
- directly use mkitab to add it into /etc/inittab
or
- drop startup scripts in /etc/rc.d/rcX.d
I know they... (4 Replies)
Discussion started by: acerlinux
4 Replies
7. Shell Programming and Scripting
Hi,
Anyone can help me on how my script will run on crontab, When I manually run my script, it work. But when I put in cron didn't work.
#crontab schedule
00 16 * * * /home/scriptdir/myscript.sh
# myscript.sh
#!/bin/bash
echo "mypassword"| sudo -S /etc/init.d/vpnclient_init start
cd... (2 Replies)
Discussion started by: fspalero
2 Replies
8. Red Hat
Hello All.
I'm trying start services as an Admin user on CentOS 7. I'm able to start the service as the user but it prompts me for a password. How do I get the user to start a service without being prompted? For example; If I attempt to start the sendmail service as my user2, I receive the... (2 Replies)
Discussion started by: bbbngowc
2 Replies
9. AIX
Hi all,
How can I close ftp port 21 on VIO server.
Best regards,
---------- Post updated at 10:06 AM ---------- Previous update was at 08:45 AM ----------
I resoved with switch to OS mode.
$ oem_setup_env (0 Replies)
Discussion started by: getrue
0 Replies
10. Solaris
Hi,
This is Solaris-10 x86. I am not able to start cron service, configured in FMRI. It is in maintenance and when I clear it, it seems like calling and failing on /etc/init.d/tcs-rtm script. I am not able to figure out, why cron is calling that script, if this failure is because of that. Cron... (5 Replies)
Discussion started by: ron323232
5 Replies
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)