Q for the admin guys,
When the server (Spark) is rebooted does a shell starts database, connection to database, and etc or would have to be the administrator log on as database admin and start the database?
If it starts from the shell how would the script look like since the dba has access to the... (1 Reply)
hi everyone
i'm running script in c-shell and i want this script to connect to admin account in order to run other script in k-shell. after that i want the script to be severed from the admin account and to continue with the regular commands
example:
my script call cs-customers
echo"starting... (16 Replies)
Hi all,
I encountered a problem where my script stops running the remaining checks after becoming an admin that is written within the script.
For example:
=========================================
#!/bin/sh
check 1 # Runs successfully
check 2 # Runs successfully
/com/bin/admin #... (1 Reply)
I'm currently a Windows admin and have wanted to jump ship to the *nix side for a while now. I've been studying both through an lpic level 1 manual as I have time (focusing on debian), and a solaris 10 cert book. The problem is I only have a handful of hours a week to study, and my current job... (3 Replies)
Can anyone create or give me a script that I can use to email a user automatically when I kill one of their processes?
Or
Can you give me a script to allow me to email a user (entering email manually) when a process is killed? Like showing what the PID was and a reason the admin killed it? Is... (2 Replies)
I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that.
Can we get "DAY" shifts in any one of the admin Job ?
Can't we have shift timings in any company ?
Eventhough the... (7 Replies)
Discussion started by: Jacktts
7 Replies
LEARN ABOUT SUNOS
atrm
atrm(1) User Commands atrm(1)NAME
atrm - remove jobs spooled by at or batch
SYNOPSIS
atrm [-afi] [ [ job #] [user...]]
DESCRIPTION
The atrm utility removes delayed-execution jobs that were created with the at(1) command, but have not yet executed. The list of these jobs
and associated job numbers can be displayed by using atq(1).
atrm removes each job-number you specify, and/or all jobs belonging to the user you specify, provided that you own the indicated jobs.
You can only remove jobs belonging to other users if you have solaris.jobs.admin privileges.
OPTIONS
The following options are supported:
-a All. Removes all unexecuted jobs that were created by the current user. If invoked by the privileged user, the entire queue will
be flushed.
-f Force. All information regarding the removal of the specified jobs is suppressed.
-i Interactive. atrm asks if a job should be removed. If you respond with a y, the job will be removed.
FILES
/var/spool/cron/atjobs spool area for at jobs
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO at(1), atq(1), auths(1), cron(1M), auth_attr(4), attributes(5)SunOS 5.10 13 Aug 1999 atrm(1)