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)
The script checks for free space stats on Oracle. If there are any tablespaces with more than 85% usage it prints the details of the tablespace. If all the tablespaces have more than 15% free space, then "All tablespaces have more than 15 pct free space" must be printed on the screen.
When I run... (2 Replies)
Hi All,
Using Expect script when I run it manually it works. But when I put the entry in crontab, the job is still running after 15 hours. The script was created as root. I don't think it's a permission issue. Any idea?
This is what I have under root crontab...
00 18 * * 1-5... (4 Replies)
Hi everyone,
I've written a script, I gave it permission by
> chmod u+x myscript
and then tried to run it with
> myscript
and it didn't work, so I've written
> ./myscript
again, it didn't work, so I've written
> set path = (. $path)
but it didn't work as well.
I have some... (6 Replies)
Hi
I need once again you help guys,
I have a php script that should call and url on the local-server, when i call the script from the browser it just prints the $str and it doesn't call the url, but when i execute the script from the shell (php sentdata.php) it works.
I checked the apache... (6 Replies)
hi i have a script called test.sh. the content is ls >> crontest.txt.
if i run manually it's giving output.but if i scheduled in crontab it's not giving output.
crontab entry:
02 * * * * /sms5/SMSHOME/eds_sh/test.sh >> /sms5/SMSHOME/eds_sh/testfile/logfile 2>&1
I am using ksh.is there... (2 Replies)
Hello all,
I'm trying to write a script to gather and send data and it works just fine at the bash command line, but when executing from CRON, it does not run properly.
My scripting skills are pretty limited and there's probably a better way, but as I said it works at the command line, but... (12 Replies)
Hi every body,
I'm getting a trouble with my script , it's supposed to return a csv file .
/usr/bin/curl -LS -D- -X GET -H "Authorization:Basic $password" -H 'Content-Type: text/csv' -L -o $OUTPUT_FILENAME $url;
But I get an empty file with :
{"ErrorCode":1001,"ErrorMessage":"Incorrect login... (0 Replies)
Hi All,
We have a requirement to Integrate Cyber-Ark with Informatica .
Basically cyberark will contain the username and password for Database.
First step will be
1)In shell Script run curl command calling cyber-Ark RESTAPI requesting the credentials and store the secret in a variable.
... (0 Replies)
Discussion started by: Praveena9102
0 Replies
LEARN ABOUT OPENDARWIN
d_passwd
d_passwd(4) File Formats d_passwd(4)NAME
d_passwd - dial-up password file
SYNOPSIS
/etc/d_passwd
DESCRIPTION
A dial-up password is an additional password required of users who access the computer through a modem or dial-up port. The correct pass-
word must be entered before the user is granted access to the computer.
d_passwd is an ASCII file which contains a list of executable programs (typically shells) that require a dial-up password and the associ-
ated encrypted passwords. When a user attempts to log in on any of the ports listed in the dialups file (see dialups(4)), the login program
looks at the user's login entry stored in the passwd file (see passwd(4)), and compares the login shell field to the entries in d_passwd.
These entries determine whether the user will be required to supply a dial-up password.
Each entry in d_passwd is a single line of the form:
login-shell:password:
where
login-shell The name of the login program that will require an additional dial-up password.
password An encrypted password. Users accessing the computer through a dial-up port or modem using login-shell will be required to
enter this password before gaining access to the computer.
d_passwd should be owned by the root user and the root group. The file should have read and write permissions for the owner (root) only.
If the user's login program in the passwd file is not found in d_passwd or if the login shell field in passwd is empty, the user must sup-
ply the default password. The default password is the entry for /usr/bin/sh. If d_passwd has no entry for /usr/bin/sh, then those users
whose login shell field in passwd is empty or does not match any entry in d_passwd will not be prompted for a dial-up password.
Dial-up logins are disabled if d_passwd has only the following entry:
/usr/bin/sh:*:
EXAMPLES
Example 1: Sample d_passwd file.
Here is a sample d_passwd file:
/usr/lib/uucp/uucico:q.mJzTnu8icF0:
/usr/bin/csh:6k/7KCFRPNVXg:
/usr/bin/ksh:9df/FDf.4jkRt:
/usr/bin/sh:41FuGVzGcDJlw:
Generating An Encrypted Password
The passwd (see passwd(1)) utility can be used to generate the encrypted password for each login program. passwd generates encrypted pass-
words for users and places the password in the shadow (see shadow(4)) file. Passwords for the d_passwd file will need to be generated by
first adding a temporary user id using useradd (see useradd(1M)), and then using passwd(1) to generate the desired password in the shadow
file. Once the encrypted version of the password has been created, it can be copied to the d_passwd file.
For example:
1.
Type useradd tempuser and press Return. This creates a user named tempuser.
2. Type passwd tempuser and press Return. This creates an encrypted password for tempuser and places it in the shadow file.
3. Find the entry for tempuser in the shadow file and copy the encrypted password to the desired entry in the d_passwd file.
4. Type userdel tempuser and press Return to delete tempuser.
These steps must be executed as the root user.
FILES
/etc/d_passwd dial-up password file
/etc/dialups list of dial-up ports requiring dial-up passwords
/etc/passwd password file
/etc/shadow shadow password file
SEE ALSO passwd(1), useradd(1M), dialups(4), passwd(4), shadow(4)WARNINGS
When creating a new dial-up password, be sure to remain logged in on at least one terminal while testing the new password. This ensures
that there is an available terminal from which you can correct any mistakes that were made when the new password was added.
SunOS 5.10 2 Sep 2004 d_passwd(4)