03-18-2007
I would look for cron jobs or at jobs that started at 19:00.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Dear Experts,
We are using Digital Unix 4.0d on Alpha DS-20 E.
/var/adm/messages showed the following error
Jul 24 19:58:37 cbehotbill2 vmunix: /BSCSprod: write failed, file system is full
Jul 24 19:58:38 cbehotbill2 last message repeated 2 times
But df -k showed
BSCS_dmn#BSCSprod ... (4 Replies)
Discussion started by: geraldwilson
4 Replies
2. Programming
When i run my C program which dynamically creates the output file, the program stops after sometime and gives the error "File size limit exceeded" even though my working directory has space.Can anyone plz help me out. (13 Replies)
Discussion started by: drshah
13 Replies
3. Solaris
Hi Guys
I need to increase the size of my /tmp swap file. What is the easiest way to do this.
Thanks
Carson (2 Replies)
Discussion started by: cmackin
2 Replies
4. UNIX for Dummies Questions & Answers
Hello -
O/S is UnixWare 7.1.4
My prefered method of copying files between servers is 'rcp', which does not recognize symbolic links; therefore, files are duplicated many times over.
To avoid this duplication, I would like to use 'tar' and/or 'cpio' and pipe them through 'rcp', but... (1 Reply)
Discussion started by: rm -r *
1 Replies
5. Solaris
hi every one ,
i know how to add swap space in ufs file system.
but i m facing problem in veritas file system .
i wants to know how will i create swap or add new swap space in existing swap space .
Note: disk under veritas volume manager control .
please help me to solve this issue . (5 Replies)
Discussion started by: samy123
5 Replies
6. AIX
Hi,
I would like to know if /tmp file system is full, wheather it will affect the peformance of application installed on AIX. if Memory and CPU are not heavily utilized.
Regards,
Manoj. (1 Reply)
Discussion started by: manoj.solaris
1 Replies
7. Solaris
Hello all,
The issue is
# df -h /tmp
Filesystem size used avail capacity Mounted on
swap 4.0G 4.0G 8.7M 100% /tmp
# du -sh /tmp/
87M /tmp
By now you probably will say that this is open file destriptor issue.
Well no, nothing... (2 Replies)
Discussion started by: click
2 Replies
8. Solaris
hi all
I am having a t5240 server in that zone is there in /var/adm/messages i am getting the following warning
WARNING: /zoneroot/zonename-zone/root/tmp: File system full, swap
space limit exceeded
if a swap is getting full what can i do.
Please use code tags next time for your... (2 Replies)
Discussion started by: nikhil kasar
2 Replies
9. Solaris
Does anyone have any advise on trying to clean up a full filesystem? I can't rm any files because of the follow:
not removed: No space left on device
Any help would be very much appreciated. (10 Replies)
Discussion started by: craigsky
10 Replies
10. Emergency UNIX and Linux Support
Hello,
This is RHEL 5.7. swap is almost full, but I am not sure, what to release and how to release space. This is production server so I would like to try all possible options before reboot.
# top
top - 00:18:26 up 327 days, 7:01, 3 users, load average: 0.16, 0.21, 0.18
Tasks: 782 total, ... (7 Replies)
Discussion started by: solaris_1977
7 Replies
LEARN ABOUT OSF1
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - Queue description file for at, batch, and cron commands
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron or specifies other characteristics for cron. Each noncom-
ment line in this file describes either one queue or a cron characteristic. Each uncommented line should be in one of the following for-
mats.
q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode
The fields in these lines are as follows: The name of the queue. Defined queues are as follows: The default queue for jobs started by at
The default queue for jobs started by batch The default queue for jobs run from a crontab file
Queues d to z are also available for local use. The maximum number of jobs that can be run simultaneously in the queue; if more
than njob jobs are ready to run, only the first njob jobs will be run. The others will be initiated as currently running jobs ter-
minate. The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser. The number of seconds to
wait before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide
limit of jobs executing (max_jobs) has been reached. The maximum number of active jobs from all queues that may run at any one
time. The default is 25 jobs. Logging level of messages sent to a log file. The default is 4. Defined levels are as follows:
level-code level
0 None
1 Low
2 Medium
3 High
4 Full
Lines beginning with # are comments, and are ignored.
EXAMPLES
The following file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run
with a nice value of 20. If a job cannot be run because too many other jobs are running, cron will wait 60 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. If a job cannot be run
because too many other jobs are running cron will wait 60 seconds before trying again to run it. b.50j20n60w
The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will log
all messages to the log file. The last two lines are comments that are ignored. max_jobs=25 log=4 # This is a comment # And so is this
FILES
Main cron directory The default location for the queue description file.
RELATED INFORMATION
Commands: at(1), cron(8), crontab(1), nice(1)
delim off
queuedefs(4)