11-24-2010
They should as they are called with these arguments.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a diskless work station.
i want to boot from a remote linux machine.
what changes i will have to do in configuration.
Plz tell me
thanks (1 Reply)
Discussion started by: hemant29
1 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I am new to Solaris.
I have installed a Solaris 10.0.
As default its shell is sh (#) and I want to modify boot records of my Solaris. I want to run some shell scripts, change shell, change PATH environment and similiar things after boot automaticially.
I don't know which files are read... (1 Reply)
Discussion started by: XNOR
1 Replies
3. SCO
I get a message saying
Not enough space to dump xxxxx pages
Press any key to reboot
Safe to power off
After rebooting it never gets to the "Press CTRL D to continue or enter password for single user" message before it goes back to "Not enough space..." message above. Vicious cycle.
... (0 Replies)
Discussion started by: deloev
0 Replies
4. Ubuntu
I have two systems in my computer . I update the ubuntu system these days and always interrupt it and exit the system . now the system cannot boot after Running local boot scripts(/etc/rc.local), it just stops there. i have to terminate the gnome display manager. what can i do with it ? thank... (0 Replies)
Discussion started by: tcb3210
0 Replies
5. AIX
Hi, can someone point me to the bootup file where I can add a samba start up script so I dont have to manually start samba everytime we reboot the server? Thanks. (8 Replies)
Discussion started by: NycUnxer
8 Replies
6. Solaris
We have a system that won't boot. It is Sun V245 that was patched yesterday with the latest Recommended 10 patch cluster. I will post what we get during the boot at the end of the email message. We have tried rebuilding the bootblk, booting from the cdrom, and running an fsck, booting into failsafe... (2 Replies)
Discussion started by: brownwrap
2 Replies
7. Red Hat
Server: Redhat 6.2
Goal: Startup script/Shutdown Script
Overview: I'm just doing a very basic test. I'm not getting chkconfig involved.
Research so far: I've found a few different ways of getting this to work, some say I can just drop the scripts in the corresponding rc directory. Others... (4 Replies)
Discussion started by: HayekSplosives1
4 Replies
8. UNIX for Advanced & Expert Users
Hi,
I got stuck in a very messy situation yesterday after attempting to resolve a filesystem full issue. The user reported that their filesystem (/var/DWS) was 100% full even after moving few files of sizes 14G, 30G and 50G out of the directory. I checked the filesystem once more after this... (5 Replies)
Discussion started by: anaigini45
5 Replies
LEARN ABOUT SUSE
tcl_callwhendeleted
Tcl_CallWhenDeleted(3) Tcl Library Procedures Tcl_CallWhenDeleted(3)
__________________________________________________________________________________________________________________________________________________
NAME
Tcl_CallWhenDeleted, Tcl_DontCallWhenDeleted - Arrange for callback when interpreter is deleted
SYNOPSIS
#include <tcl.h>
Tcl_CallWhenDeleted(interp, proc, clientData)
Tcl_DontCallWhenDeleted(interp, proc, clientData)
ARGUMENTS
Tcl_Interp *interp (in) Interpreter with which to associated callback.
Tcl_InterpDeleteProc *proc (in) Procedure to call when interp is deleted.
ClientData clientData (in) Arbitrary one-word value to pass to proc.
_________________________________________________________________
DESCRIPTION
Tcl_CallWhenDeleted arranges for proc to be called by Tcl_DeleteInterp if/when interp is deleted at some future time. Proc will be invoked
just before the interpreter is deleted, but the interpreter will still be valid at the time of the call. Proc should have arguments and
result that match the type Tcl_InterpDeleteProc:
typedef void Tcl_InterpDeleteProc(
ClientData clientData,
Tcl_Interp *interp);
The clientData and interp parameters are copies of the clientData and interp arguments given to Tcl_CallWhenDeleted. Typically, clientData
points to an application-specific data structure that proc uses to perform cleanup when an interpreter is about to go away. Proc does not
return a value.
Tcl_DontCallWhenDeleted cancels a previous call to Tcl_CallWhenDeleted with the same arguments, so that proc will not be called after all
when interp is deleted. If there is no deletion callback that matches interp, proc, and clientData then the call to Tcl_DontCallWhen-
Deleted has no effect.
KEYWORDS
callback, delete, interpreter
Tcl 7.0 Tcl_CallWhenDeleted(3)