Hi all...
In my Unix system a program exists called "daemon2" which is responsible to enqueue program executions. For example, if I want to make the system to enqueue lpr executions for certain users, I call daemon2 with lpr as the parameter.
Is there an equivalent in Linux?
Thanks
Jaime (0 Replies)
Hi all,
I am preparing for a worst case scenario. Say i have a production server A, should A fails ( for whatever reason), i want another server B to take over. How can i move everything from A to B? Assuming i have regular backup of A.
I've searched in the forums, and briefly came across... (4 Replies)
In IBM Mainframe they have something called ACF2 rule which is essentially used to control the dataset access. It is kind of a list-based access control for mainframe datasets.
Is there anything equivalent to ACF2 available in Unix ?
Thanks
Rabi (1 Reply)
I moved to a Linux system from Windows a few months ago. Most of the programs I had been using were already native to Linux (Firefox, the GIMP, Pari, etc.) and most others I found a close enough program (Crimson Editor -> gedit, Visual Studio -> KDevelop, Primo -> Morain's ECPP).
Now I'm down... (1 Reply)
Hi Guys,
I am used to configuring DHCP on Solaris and foreach subnet added I place a corresponding entry in /etc/netmasks. I am now looking at configuring DHCP on linux, is there an equivalnet entry required somewhere or is this not needed in linux
Thanks (3 Replies)
Hi,
I need to mount a replicated nfs4 export on a number of AIX and Redhat hosts. To get the failover on the clients working smoothly, I need to change certain values on the AIX boxes like nfs_v4_fail_over_timeout, timeo and retrans values. Since I have no clue about Linux, I am not quite sure... (1 Reply)
I have a folder called "log" which has a few sub-folders say "fda" "fd7" "fdd" "fd6 .... "
I wish to fire the below command inside each subfolder starting with the folder with the latest time stamp.
grep "$greptime.*exit" Prod.$(hostname).log | grep $fdrdate_new
If the seach did not yield... (3 Replies)
We have asked UNIX.com users over the years what is their favorite editor and why. Here is the top three answers.
Here is a new YT video on this question:
What Editor Does Everyone Use?
https://youtu.be/gqE8RTZZt9g
Of course, vi was the overwhelming favorite.
Credits:
1080 HD... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT OPENDARWIN
end
GET_END(3) Library Functions Manual GET_END(3)NAME
get_end, get_etext, get_edata - get values of UNIX link editor defined symbols
SYNOPSIS
#include <mach-o/getsect.h>
unsigned long get_end();
unsigned long get_etext();
unsigned long get_edata();
DESCRIPTION
These routines provide a stopgap measure to programs that use the UNIX link-editor defined symbols. Use of these routines is very strongly
discouraged. The problem is that any program that is using UNIX link editor defined symbols (_end, _etext or _edata) is making assumptions
that the program has the memory layout of a UNIX program.
This is an incorrect assumption for a program built by the Mach-O link editor. The reason that these routines are provided is that if very
minimal assumptions about the layout are used and the default format and memory layout of the Mach-O link editor is used to build the pro-
gram, some things may work by using the values returned by these routines in place of the addresses of their UNIX link-editor defined sym-
bols. So use at your own risk, and only if you know what your doing. Or better yet, convert the program to use the appropriate Mach or
Mach-O functions. If you are trying to allocate memory use vm_allocate(2), if you are trying to find out about your address space use
vm_region(2) and if you are trying to find out where your program is loaded use the dyld(3) functions.
The values of the UNIX link-editor defined symbols _etext, _edata and _end are returned by the routines get_etext, get_edata, and get_end
respectively. In a Mach-O file they have the following values: get_etext returns the first address after the (__TEXT,__text) section, note
this my or may not be the only section in the __TEXT segment. get_edata returns the first address after the (__DATA,__data) section, note
this my or may not be the last non-zero fill section in the __DATA segment. get_end returns the first address after the last segment in
the executable, note a shared library may be loaded at this address.
SEE ALSO ld(1), dyld(3)Apple Computer, Inc. April 10, 1998 GET_END(3)
11-29-2011
