04-23-2002
Sounds like you have either a daemon or a cron job that is doing this.
If you can't find where this is running from you should have a cron log. It might be under /var/adm/cron/log. This file will tell you what is running from cron, if it doesn't appear obvious in the crontab.
OR if you can change the location of the logfile, I would try that also.
BTW, when you loaded this app, did it give you any options to set? like where the logfile goes, what the parms are, etc...
Hope this helps...
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
there is a directory eg. /home/edp/ , all the files under this directory :
1. the file and directory owner is "user1" ,
2. the permission is 644
I want everyone hv permission to overwrite all files and write a new file to it , but I want the file owner and permssion keep unchange , could... (1 Reply)
Discussion started by: ust
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
When I listed one directory in Sun, it showed that :
-rwsr-xr-x 1 root bsmbin 78004 Oct 21 2004 bsmprsm
I don't know meaning of the character "s" in "rws" above. I have searched in Sun admin documents but no result. Would you please explain it ? :)
Thank you so much. (1 Reply)
Discussion started by: msg098
1 Replies
3. Cybersecurity
Hello,
i need some help/advice on how to solve a particular problem.
these are the users:
|name | group |
---------- ---------------
|boss | department1 |
|assistant | department1 |
|employee | department1 |
|spy | department2 |
this is the... (0 Replies)
Discussion started by: elzalem
0 Replies
4. UNIX for Dummies Questions & Answers
i have two user named sourav and jishu.
i have created a file named source.txt in sourav.
i made another user called shovon.
i want to give read write permission of souce.txt for shovon but not for jishu.
how can i set permission only for jishu ? (1 Reply)
Discussion started by: sourav_ray
1 Replies
5. Solaris
I can't get the exact error message because I am at home, but on Solaris 10u5 machine I have at work, a few services are stuck in the maintenance state with the following error message in the individual service logs (/var/svc/log/FMRI:instance.log):
Cannot chdir: permission denied
Fortunately... (2 Replies)
Discussion started by: ilikecows
2 Replies
6. Solaris
hi frnds
can u explain
/etc/shadow file have read and write permissions for root only
but while normal user changes his passwd it also updated in that file whats the logic behind that. (2 Replies)
Discussion started by: sravan ega
2 Replies
7. Shell Programming and Scripting
Hi All,
https://www.unix.com/unix-advanced-expert-users/105758-chmod-parent-sub-directories.html
I have to change permission for the directories and subdirectories in single command
when googled i found some updates but i understand what is switch.
If there is a command please... (2 Replies)
Discussion started by: thelakbe
2 Replies
8. Emergency UNIX and Linux Support
Hello All, On my SuSE system, I have wtmp log this log file permission is 644 but every reboot the file permission rollback to 664. In the logrotate.conf and logrotate.d/wtmp files the wtmp logrotate set to 644. I would like to know, which "file" or "script" modify the wtmp log to rollback to... (7 Replies)
Discussion started by: kalaso
7 Replies
9. AIX
I'm trying to set the permission for the syslog log file in syslog,conf.
---------
The below is my configuration file
## example:
# "mail messages, at debug or higher, go to Log file. File must exist."
# "all facilities, at debug and higher, go to console"
# "all facilities, at crit or... (1 Reply)
Discussion started by: novaothers
1 Replies
10. UNIX for Dummies Questions & Answers
Only kernel can write to a directory file. Then what does write permission for a directory imply? (2 Replies)
Discussion started by: vijaysy
2 Replies
LEARN ABOUT OPENSOLARIS
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1 A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.11 1 Mar 1994 queuedefs(4)