07-24-2013
Joing Linux systems to AD and move to OU
Hi,
We have joined Linux systems ( RHEL 6.3 ) to Windows AD ( 2008 R2 ).
System has been placed in the deafault location 'Computers' in AD. Then we manually move the systems to the respective OU.
Is there any option to specify OU location at the time of domain joining ?
We are using below command to join the systems.
# net ads join -U Administrator
5 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi,
I need to backup files on our Solaris machines onto a windows machine. I have Samba installed. Is it possible to backup these files on Solaris/Linux machines onto a Windows machine.
Thanks
Aravind (1 Reply)
Discussion started by: aravind_mg
1 Replies
2. Linux
Please please tell me why/how you do it!!! I couldn't!
Does anyone in here do it? If so... wwwwhhhhyyyyy? :) (2 Replies)
Discussion started by: TonyChapman
2 Replies
3. UNIX for Dummies Questions & Answers
I am new to the Unix/Linux environment, can someone give me a idea of what the differences is between all of the Linux systems. Example, Redhat, Suse etc..
Thanks
MF (2 Replies)
Discussion started by: MFARMER
2 Replies
4. UNIX for Dummies Questions & Answers
Hello!
I have seen similar questions asked about how to become a system administrator. Most would say experience is more important than just getting a certificate and even a degree. However, I haven't found a good information how to build experience from a newbie to entry-level systems... (8 Replies)
Discussion started by: sideburn
8 Replies
5. UNIX for Dummies Questions & Answers
Hi
I have to move files between file systems but files in new file system must have the same attributes as in old one (privileges, time stamp etc).
Which tool is best :
- ufsdump / ufsrestore
- tar
- cpio
- pax
- dd
- mv
Or maybe there is sth else, you suggest to use.
Thx for help (5 Replies)
Discussion started by: presul
5 Replies
LEARN ABOUT LINUX
ssignal
GSIGNAL(3) Linux Programmer's Manual GSIGNAL(3)
NAME
gsignal, ssignal - software signal facility
SYNOPSIS
#include <signal.h>
typedef void (*sighandler_t)(int);
int gsignal(intsignum);
sighandler_t ssignal(int signum, sighandler_t action);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
gsignal(), ssignal(): _SVID_SOURCE
DESCRIPTION
Don't use these functions under Linux. Due to a historical mistake, under Linux these functions are aliases for raise(3) and signal(2),
respectively.
Elsewhere, on System V-like systems, these functions implement software signaling, entirely independent of the classical signal(2) and
kill(2) functions. The function ssignal() defines the action to take when the software signal with number signum is raised using the func-
tion gsignal(), and returns the previous such action or SIG_DFL. The function gsignal() does the following: if no action (or the action
SIG_DFL) was specified for signum, then it does nothing and returns 0. If the action SIG_IGN was specified for signum, then it does noth-
ing and returns 1. Otherwise, it resets the action to SIG_DFL and calls the action function with argument signum, and returns the value
returned by that function. The range of possible values signum varies (often 1-15 or 1-17).
CONFORMING TO
These functions are available under AIX, DG/UX, HP-UX, SCO, Solaris, Tru64. They are called obsolete under most of these systems, and are
broken under Linux libc and glibc. Some systems also have gsignal_r() and ssignal_r().
SEE ALSO
kill(2), signal(2), raise(3)
COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
2007-07-26 GSIGNAL(3)