11-18-2009
The PC server should be the master, right? It should initiate rsync commands to the unix boxes it serves.
Don't run rsync "realtime", every 30 minutes is often enough. Schedule rsync on a round-robin basis. If you have dozens of unix boxes, then run rsync less frequently so that each unix box has time to sync up.
9 More Discussions You Might Find Interesting
1. Programming
i have written a TCP client server application in c under unix. The windows systems should also be alowed to connect to the TCP server running on linux.So i wrote a small client application in VB using winsock. The client and server works fine in the linux environment. When i tried to connect the... (0 Replies)
Discussion started by: collins
0 Replies
2. IP Networking
Hi,
I am doin a project that'll work as a normal Explorer on Windows
but the best thing is it'll be exploring the content of a UNIX server.
The application would be runnin on the windows platform with probably a
FTP server on UNIX server.
How i should proceed? (2 Replies)
Discussion started by: ziaullahk
2 Replies
3. Windows & DOS: Issues & Discussions
We have a Windows Server 2003 box and I'd like to share a drive with a Sun Solaris box so that the Sun Solaris box can copy files to/from the Windows Server 2003.
I believe that Windows Services for UNIX 3.5 will allow me to do this, can anyone comfirm this ?
Also, any links on how to... (1 Reply)
Discussion started by: markgrimes
1 Replies
4. UNIX for Dummies Questions & Answers
Hello All,
I need your help with this, i appreciate all your help that you can give.
Windows NT Domains
Connect Windows XP as a domain client to both systems, Windows Server 2003 and Unix.
Secure shell
Set up secure shell on Linux (ssh). Set up secure client on Windows XP. Putty?
I... (1 Reply)
Discussion started by: italia
1 Replies
5. Windows & DOS: Issues & Discussions
Hi people,
I'm trying to configure the OpenSSH in my win server 2003 to accept connection with public/private keys, without password.
I research all over internet sites about, almost all them, have the same instructions that doesn't work.
I can just get a sFTP connection with password without... (0 Replies)
Discussion started by: laurentiis
0 Replies
6. Shell Programming and Scripting
Hi All,
I am trying to connect from Unix machine to Windows 2003 server using passphrase method. It is connecting to the server and the connection is immediately closing. Below is the stack trace. Can anyone let me know what wrong with it?
cwadmin@iut1wps1:/home/cwadmin> ssh username@targetip... (1 Reply)
Discussion started by: vijayin
1 Replies
7. Shell Programming and Scripting
Hi,
I have generated a Public/Private Key Pair in Solaris Unix (source) server and deployed the Public key in Windows 2003(target) server .ssh directory of user profile.
When i try to connect(ssh, scp, sftp) from Unix, i'm getting below error message.
Sun_SSH_1.1, SSH protocols 1.5/2.0,... (0 Replies)
Discussion started by: ajaykumarb
0 Replies
8. UNIX and Linux Applications
Hi,
i have a server installed samba+openldap (pdc). Need to migration windows server 2003 (active directory) object users, computers.
Where you can read how to do it? Or can tell me how to do it?
Thanks.
P.S. Sorry for bad english (0 Replies)
Discussion started by: ap0st0l
0 Replies
9. UNIX for Advanced & Expert Users
Hi,
I am new unix,
In the unix server we have two folders
1. /home/directory/sub1/
2. /home/directory/sub2/
Under each sub we have some other subfolders also.
Here my question is
I want to create sub2(including subfolder of this) as share drive to windows 2003 server.
Can... (7 Replies)
Discussion started by: mabu.ps
7 Replies
LEARN ABOUT DEBIAN
slack.conf
slack.conf(5) File Formats Manual slack.conf(5)
NAME
slack.conf - configuration file for slack
DESCRIPTION
The file /etc/slack.conf contains configuration information for slack(8) and its backends. It should contain one keyword-value pair per
line, separated by an '=' sign. Keywords must consist solely of capital letters and underscores. Values may take any appropriate format,
but must not begin with a space. Comments start with '#', and all text from the '#' to the end of a line is ignored. Trailing whitespace
on lines is ignored. Empty lines or lines consisting of only whitespace and comments are ignored.
Valid keywords are:
SOURCE The master source for slack roles. It can be in one of four forms:
o /path/to/dir
Use a local directory.
o somehost:/path/to/dir
Use given directory on a remote host via rsync over SSH.
o rsync://somehost/module
Use module on a remote rsyncd server (directly over the network).
o somehost::module
Use the rsync daemon protocol over SSH to the given host. See "USING RSYNC-DAEMON FEATURES VIA A REMOTE-SHELL CONNECTION" in
rsync(1)
All forms of SOURCE are passed directly to rsync, so you can do things like add "user@" before the host on any remote forms. For
more about what rsync can do, see its manual page, of course.
For the last form, however, we do a little magic. rsync treats the last two forms equivalently, so we overload the last form by
automatically passing "-e ssh" to rsync when we see it. This hack lets us tell slack to use this nice feature of rsync just using
the SOURCE config option.
ROOT The root filesystem into which to install slack roles. Usually '/'.
ROLE_LIST
The location of the role list, which lists the roles to be installed by default on each host.
This can be a path relative to the source, or can be an entirely separate location if it starts with a slash or a hostname (option-
ally preceeded by user@).
CACHE A local cache directory, used as a local mirror of the SOURCE.
STAGE A local staging directory, used as an intermediate stage when installing files.
BACKUP_DIR
A directory in which to keep dated backups for rollbacks.
EXAMPLE
A typical file might look like this:
# slack.conf configuration file
SOURCE=slack-master:/slack # source is on a remote
# host named "slack-master"
ROLE_LIST=slack-master:/roles.conf
ROOT=/
CACHE=/var/cache/slack
STAGE=/var/lib/slack/stage
BACKUP_DIR=/var/lib/slack/backups
FILES
/etc/slack.conf
SEE ALSO
slack(8), rsync(1)
File formats 2005-05-23 slack.conf(5)