Hello guys
I am new to using Unix and was hoping somebody could help me. Essentially, I am trying to clean out my database. For example, I have a directory filled with 100s of analytics and I want to know if they are used by any other analytics or if they are used by the front end user interface platforms. When I run
it returns other analytics where this analytic is used. But i would like to run something that means i don't have to go through them one by one.
Thank you very much. Any help is appreciated
Hi,
I have a directory which contains files.This Directory keeps getting in new files from time to time.I want to maintain only 15 files in that directory at any time and the old files should be deleted.
Eg:
Directory 'c' @'a/b/c contains:
1_a
2_a
3_a...
I want to delete all the old... (2 Replies)
Hi All,
when I use the following analytic function in sql prompt, i am getting the result
count(emp_no) over (partition by emp_no )
/* select count(emp_no) over (partition by emp_no ) from temp */
but when i use the same analytic function in Pro*c i get the following error
Error... (2 Replies)
Hi Friends,
I am new to this , I am working on AIX system and my scenario is to retrive the files from remote system and remove the files from the remote system after retreving files. I can able to retrieve the files but Can't remove files in remote system. Please check my code and help me out... (3 Replies)
Hi all, I have developed a shell script to copy the files from source to destination and simultaneously to delete the copied files in source. I can copy the files but the files cannot be deleted in source side. (3 Replies)
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Hi All,
I am trying to debug my core file using kdb.
When I try to get the stack trace I am facing this error.
core mapped from @ 700000000000000 to @ 70000000306fc04
Preserving 1680415 bytes of symbol table
Dump does not start with valid magic number
WARNING: Possibly truncated or... (2 Replies)
#!/bin/bash
#
name=$1
type=$2
number=1
for file in ./**
do
if
then
filenumber=00$number
elif
then
filenumber=0$number
fi
tempname="$name""$filenumber"."$type"
if (4 Replies)
Discussion started by: TheGreatGizmo
4 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 208SYSTEMD-RUN(1)