|
You should use the dns on the DC Server for all computers on your network including the DC.
Then you set up a zone for every domain you want the dns to handle, it doesn't matter if this domain already exists outside the LAN, it will serve the records you have stored in the dns to all computers on the network. It will only use the root hints or forwarders for the domains it does not handle.
|
|
|
|
|
--@--.--- [~/public_html/user/unixp]# ls
./ ../ 1 a/ b/ ls
--@--.--- [~/public_html/user/unixp]# ls a
./ ../ a b
--@--.--- [~/public_html/user/unixp]# ls b
./ ../ b c
--@--.--- [~/public_html/user/unixp]# find ./b -name 'ls a' -exec rm {}\;
find: missing argument to `-exec'
Here i want to delete common files between directories A and B that is b from directory b.
|
|
|
|
|
nt_virus wrote: 'ls a'
Are these normal or back quotes?
|
|
|
|
|
yes. it is .. Single quote. 1-Key right of L.
|
|
|
|
|
nt_virus wrote: yes. it is .. Single quote. 1-Key right of L.
I think it should be the backquote '`' character which is just below the Esc key on my keyboard. I think in your case you have passed the string 'ls a' to the -name condition, whereas you actually want the output from the ls a command, so it needs to be put in backquotes for the shell to interpret correctly.
|
|
|
|
|
I rectified with backquote now..
----@---.-- [~/public_html/user/unixp]# find ./b -name `ls -a` -exec rm {}\;
find: warning: Unix filenames usually don't contain slashes (though pathnames do). That means that '-name ./' will probably evaluate to false all the time on this system. You might find the '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ ./'.
find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]
now ?
|
|
|
|
|
Erm, you changed ls a to ls -a !
|
|
|
|
|
----@---.-- [~/public_html/user/unixp]# find ./b -name `ls a` -exec rm {}\;
find: warning: Unix filenames usually don't contain slashes (though pathnames do). That means that '-name ./' will probably evaluate to false all the time on this system. You might find the '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ ./'.
find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]
why this happening
|
|
|
|
|
nt_virus wrote: find: warning: Unix filenames usually don't contain slashes (though pathnames do). That means that '-name ./' will probably evaluate to false all the time on this system. You might find the '-wholename' test more useful, or perhaps '-samefile'. Alternatively, if you are using GNU grep, you could use 'find ... -print0 | grep -FzZ ./'.
find: paths must precede expression
Usage: find [-H] [-L] [-P] [path...] [expression]
That's why! It has given you a complete explanation of the issue. Your ls command is still listing the directories with trailing '/' characters and the find command does not like it. I don't know which version of UNIX this is but there should be an option to suppress these characters. Take a look at the man page for ls . Also check whether you have alias ed the command to set some default options.
|
|
|
|
|
You're on the right track. You don't need the -name parameter, though you'll probably want to make sure that each thing "find" locates is a file, and not something else like a directory or symlink.
"find" can be somewhat annoying in that it will spit out the entire relative pathname for each file it finds. That is,
find ./dirA -type f
will yield
./dirA/file1<br />
./dirA/file2
To get around that, just chdir into dirA before doing the find.
$ cd dirA
$ touch file1 file2 file4 file5
$ cd ../dirB
$ touch file1 file3 file5 file6
$ cd ..
$ ls dirA
file1 file2 file4 file5
$ ls dirB
file1 file3 file5 file6
$ cd dirA
$ find . -type f -exec rm -f ../dirB/{} \;
$ cd ..
$ ls dirA
file1 file2 file4 file5
$ ls dirB
file3 file6
$
I would have answered earlier, but I only joined last week. Hope this late reply helps.
|
|
|
|
|
hello
Anyone has idea what's the difference between Norton Ghost Suite (http://www.symantec.com/business/ghost-solution-suite) and regular Norton Ghost (http://www.symantec.com/norton/ghost)
I looked at system requirement looks like "Norton Ghost Suite" supports Windows 2003 Enterprise, regular "Norton Ghost" don't.
For Windows 7 Enterprise, seems like both can do the job.
Am I right ..?
Thanks
dev
|
|
|
|
|
Symantec Ghost solution suite is the original Disk cloning program (made by Binary Research) made for cloning disks so that you can install many identical computers in a corporate environment.
Norton Ghost is the old Powerquest DriveImage which IMHO is nothing more than a backup program for home use on steroids.
Symantec = Business users.
Norton = Home users.
|
|
|
|
|
|
no need to reply if you can't add anything useful to the thread.
|
|
|
|
|
Is there any term available named "Robot" which is related with CD writing/burning Software?
Best Regards,
Saravanan T
|
|
|
|
|
The only one I can think of would be a device used to remove and insert CD's into the drive for you.
|
|
|
|
|
Hi All,
How to protect CD/DVD from copying the data file (e.g., *.PDF).
Best Regards,
Saravanan T
|
|
|
|
|
use power2go software, this will protect your CD or DVD with password and encryption.
|
|
|
|
|
Yeah, but once those are entered, there is nothing stopping the user from copying the data off the disk and burning it to another one.
|
|
|
|
|
Do not post the same question to multiple forums. This is called spamming and is cosidered very rude.
|
|
|
|
|
Hello webmaster,
please cancel my account, because i dont need this membership any longer.
I have not found a button to cancel my membership.Where is it on your website?
So you can manually cancel my account?
My Login-Name was: nicole2222
The link for unsubscribing in your mail was not working.
thanks.
nicole
|
|
|
|
|
What do you mean? do you like to unsubscribe the newsletter ?
Or you want to remove your login ?
Do you think this is the right place to talk about this ?
|
|
|
|
|
You would need to file this request in 'Suggestions and Bug Reports' forums.
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep!
|
|
|
|
|
Hi, As far as I know, windows grant the permission to the file on the server based on the SID of the user account.
But my laptop that join to the domain which already has the local user account and password that the same as the domain user account and password when it mapped the network drive, it could map successfully and could do anything as the permission which is grant to my domain user account.
Why this is possible while the SID of my domain user account is difference with the SID of my local user account?
Thank in advance!!!
|
|
|
|
|
Mapping drive doesn't use a SID. It uses a username and password which can be the same between two accounts in different SAMs. When you mapped the drive, you did so using the account in the domain SAM and not the local account.
Other than that, your description of the circumstances isn't entirely clear.
|
|
|
|