02-15-2008
Correct - it makes no sense in unix. You do not "commit idle processes" in unix.
If I understand what you mean, init does that on it's own.
8 More Discussions You Might Find Interesting
1. SCO
Hi,
Please let us know of any possiblity of identifying and killing unix proces invoked externally (by an external tool which does not create a session). 'who' command gives idle time of sessions. But what we are looking for is idle time of a process. 'ps' command gives the elapsed/running... (1 Reply)
Discussion started by: vbalajis
1 Replies
2. SCO
Hi.
Am a unix 5.o.5 user. I need to schedule a program to be running everyday at 12 midnight. How do i proceed. I need help.
Also what is the maximum size that sco unix can conveninetly handle. I keep getting this message. "Filesystem greater than device which it is curently located. Pls backup... (2 Replies)
Discussion started by: uzomaok
2 Replies
3. AIX
good morning
Can you explain to me what is a "commit" (aix 5.3) ?
There is no man for this command.
thank you (1 Reply)
Discussion started by: pascalbout
1 Replies
4. Shell Programming and Scripting
I would like to run a cvs diff to check which files have been changed and then cvs commit these changed files. Does anyone have a shell script which will automate this process? (1 Reply)
Discussion started by: alangibson
1 Replies
5. UNIX for Advanced & Expert Users
Hi ,
can u please any one of you give solution for this ..
when am tryring to commit files from the CVS in Myeclipse J2ee Environment . that i coundnt able to commit and getting the Following error message
cvs :'root' is not allowd to commit files'
am using redhat enterprise 5 Server . (1 Reply)
Discussion started by: rksubash
1 Replies
6. Shell Programming and Scripting
I am writing a unix shell script for the archive purge job.
During purging, the records will be deleted one by one. I didnot mention anything about db2 commit. By default, the records are commited one by one. Now I need to give commit for every 50 records deletion.
The deletion part is as... (0 Replies)
Discussion started by: kmanivan82
0 Replies
7. Shell Programming and Scripting
Hi All,
I have written a shell script in which i am updating records in a table. It is a PL/SQL block. I have to use PL/SQL block as i am using bms_application_info.set_module package
But the problem is once the script completes, i cannot see the updated records in Table. I mean result is... (0 Replies)
Discussion started by: Amit.Sagpariya
0 Replies
8. Shell Programming and Scripting
Is someone help me to achieve my goal
I am working on a script actually script is working fine .The goal of script is restrict the user for something like while he is doing tocommit in repository he will commit with comment and with some parameter....here I have one more requirement and that is... (0 Replies)
Discussion started by: anuragpgtgerman
0 Replies
SAVECORE(8) System Manager's Manual SAVECORE(8)
NAME
savecore - save a core dump of the operating system
SYNOPSIS
savecore dirname [ system ]
DESCRIPTION
Savecore is meant to be called at the end of the /etc/rc file. Its function is to save the core dump of the system (if one was made) and
to write a reboot message in the shutdown log.
It saves the core image in the file dirname/core.n and its corresponding namelist in dirname/unix.n. The second argument is the namelist
for the system which made the core image; the current system is always assumed to be /unix. The trailing ".n" in the pathnames is replaced
by a number which grows every time savecore is run in that directory.
Before savecore writes out a core image, it reads a number from the file dirname/minfree. If there are fewer free blocks on the file sys-
tem which contains dirname than the number obtained from the minfree file, the core dump is not done. If the minfree file does not exist,
savecore always writes out the core file (assuming that a core dump was taken).
Savecore also writes a reboot message in the shut down log. If the system crashed as a result of a panic, savecore records the panic
string in the shut down log too.
If savecore detects that the system time is wrong because of a crash (the time in the core image is after the current time), it will reset
the system time to its best estimate of the time, which is the time in the core image plus the elapsed time since the reboot. It announces
the time that it set when this occurs.
FILES
/usr/adm/shutdownlogshutdown log
/unix current UNIX
BUGS
The method used to determine whether a dump is present, and to prevent the same core image from being saved multiple times, is not elegant.
This information should be passed to init by the system; however, this is difficult because the system may have to be rebooted a second
time if the root filesystem is patched.
3rd Berkeley Distribution SAVECORE(8)