09-06-2013
Why not using a GUI tool like WinSCP to copy the files?
10 More Discussions You Might Find Interesting
1. HP-UX
Good day,
i would like to get some advice, how will i execute my script in hp ux servers, and how to configure rsh and rexec.
thanks (2 Replies)
Discussion started by: kenshinhimura
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
Just wanted to know, how can I ftp/transfer/copy a (design.tar.gz) archive from a Unix Server (sdmc222.sdmc.cp-srv.com) which is at a remote location, to my Windows Desktop. Obviously, it is not possible at cmd prompt on my Windows using the following commands :-
ftp... (3 Replies)
Discussion started by: marconi
3 Replies
3. 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
4. Shell Programming and Scripting
Hi Experts,
I have a requirement where i need to setup a batch job which runs everymonth and move the pdf files from unix server to windows servers.
Could some body provide the inputs for this.
and also please provide the inputs on how to map the network dirve in the unix like that... (1 Reply)
Discussion started by: ger199901
1 Replies
5. Shell Programming and Scripting
I'm trying to write a Perl script where a file from a UNIX server box connects to a Windows server box and copies that file into the Window box.
The main problem I have right now is that whenever I try to connect to the Windows box, the connection is refused.
The error message that always pops... (2 Replies)
Discussion started by: kooshi
2 Replies
6. Shell Programming and Scripting
Can anybody please help me on how to code for the below requirement:
I need to write a shell script (on different unix server) to copy files from multiple folders (ex. BRN-000001) from one windows server (\\boldls-mwe-dev4)to a different windows server(\\rrwin-ewhd04.ecomad.int). This shell... (4 Replies)
Discussion started by: SravsJaya
4 Replies
7. Shell Programming and Scripting
Hi, I am new to this subject.....Can someone please help me out with the script...
unix usernm "sdhftst"
unix pwd "chsd13"
windows usernm "dfghtst"
windows pwd "chsd13"
path..../xxx/xxxxx/xxxxxx/xxxxxxx
please can u get me a script...its only one file to get ftp.
Thanks... (2 Replies)
Discussion started by: himakiran9
2 Replies
8. Windows & DOS: Issues & Discussions
Hello,
How can I please have a program automatically upload some files from a ubuntu server to my machine desktop that is running windows XP? I would like to be able to do that from the windows machine itself.
Thanks, (3 Replies)
Discussion started by: Pouchie1
3 Replies
9. Windows & DOS: Issues & Discussions
Hi all,
I'm a newbie to unix. My requirement is to create an automation script which will transfer a zipped folder from my/remote desktop to an unix server. Tools lik WinSCP shouldnt be used. No manual moving. I use putty to connect to server. I couldnt find any help on this topic. Should i use... (3 Replies)
Discussion started by: sherin22
3 Replies
10. Proxy Server
I have a requirement of following -
1. Transfer excel spreadsheet from desktop to unix server
2. Open the spreadsheet and read the sql row by row at a time
3. Run each sql on database using unix and then send output back to spreadsheet that was uploaded earlier and then transfer file back to... (12 Replies)
Discussion started by: Analabhatla
12 Replies
boinc(1) boinc(1)
NAME
boinc - The BOINC core client program.
SYNOPSIS
boinc [options]
DESCRIPTION
The BOINC "core client", boinc, is the heart of BOINC. It controls which project applications are run on your computer, downloading
"Workunits" and uploading the "Result" files from completed tasks. boinc is usually run in the background, ideally as a daemon. It can then
be controlled either by a graphical tool called the BOINC Manager, boincmgr(1), or a command-line tool called boinccmd(1), by means of Re-
mote Proceedure Calls (RPCs) over port 31416.
The BOINC core client can be controlled by command-line options, configuration files, and environment variables. Standard usage is simply
to start the client running in the background.
OPTIONS
These command-line options for boinc can be used to control how BOINC is started. Once the client has started, you should use a separate
program, (boincmgr(1) or boinccmd(1)) which communicates with it by means of Remote Proceedure Calls (RPCs).
--help show options
--version
show version info
--exit_when_idle
exit when there are no results
--show_projects
show attached projects
--detach_project URL
detach from a project
--reset_project URL
reset (clear) a project
--attach_project URL key
attach to a project
--update_prefs URL
contact a project to update preferences
--run_cpu_benchmarks
run the CPU benchmarks
--check_all_logins
for idle detection, check remote logins too
--allow_remote_gui_rpc
allow remote GUI RPC connections
--gui_rpc_port port
port for GUI RPCs
--redirectio
redirect stdout and stderr to log files
--dir path
use given dir as BOINC home
--no_gui_rpc
Omits creation of a socket as required for the remote control of the client. Consequently the client cannot be controlled by exter-
nal tools like GUIs (boincmgr etc.) or the console command tool (boinccmd).
--daemon
run as daemon
--exit_before_start
exit right before starting a job
--exit_after_finish
exit right after finishing a job
--insecure
disable app sandboxing
--launched_by_manager
core client was launched by Manager
--run_by_updater
set by updater
ACCESS CONTROL FOR GUI RPC
By default the core client accepts GUI RPC connections only from programs on the same host, which means that any user on this host can con-
trol the core client.
SEE ALSO
boinccmd(1), boincmgr(1)
<http://boinc.berkeley.edu/wiki/Client_configuration_(advanced)>
COPYRIGHT
Copyright (C) 2007-2008 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or
any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts.
April 06, 2008 boinc(1)