Hi, totally new to linux base using windows when started learning and using computers.
but i remember that one pc was there , look alike windows desktop, but could not do the task as windows just click and open and view edit etc. But, you could do a little differently even saving in and opening... (8 Replies)
Hi All,
I wanted to run a small socket application written in C on windows.
The code was written for GNU/linux..the compiler on windows CodeBlocks complains about the sys headers.
is there an equivalent for windows ? (4 Replies)
forgive me if i am posting this question in wrong forum.
I have a rsync script that runs on one server for rsync with another server (both linux)
.
Now I want to get control of that script from my windows 7 machine. Means I want to run that script from my windows machine whenever i want... (1 Reply)
I have a virtual machine with RedHat. It has a command-line tool X that takes an input file + some control parameters, performs some processing and generates some input files. I have a Windows XP/Server 2003 box where an app Y is running. What I need to do is to control X from Y. That is, given an... (1 Reply)
OK: apologies (well) in advance if this is as stupid a question as it gets.
I need to change the 'owner' on certain files and folders within my Linux web hosting account.
Unfortunately I use Windows XP and now need some kind of Windows application that can open a window within XP that lets me... (1 Reply)
Hi
i need some help , i would like to run a GUI application on windows from unix
i dont need to see the gui just to activate it from remote .
it shoud be from CLI on the unix .
thanks
GUY (1 Reply)
WINESERVER(1) Windows on Unix WINESERVER(1)NAME
wineserver - the Wine server
SYNOPSIS
wineserver [options]
DESCRIPTION
wineserver is a daemon process that provides to Wine roughly the same services that the Windows kernel provides on Windows.
wineserver is normally launched automatically when starting wine(1), so you shouldn't have to worry about it. In some cases however, it can
be useful to start wineserver explicitly with different options, as explained below.
OPTIONS
-d[n], --debug[=n]
Set the debug level to n. 0 means no debugging information, 1 is the normal level, and 2 is for extra verbose debugging. If n is
not specified, the default is 1. The debug output will be sent to stderr. wine(1) will automatically set the debug level when start-
ing wineserver if the +server option is set in the WINEDEBUG variable.
-f, --foreground
Make the server remain in the foreground for easier debugging, for instance when running it under a debugger.
-h, --help
Display a help message.
-k[n], --kill[=n]
Kill the currently running wineserver, optionally by sending signal n. If no signal is specified, sends a SIGINT first and then a
SIGKILL. The instance of wineserver that is killed is selected based on the WINEPREFIX environment variable.
-p[n], --persistent[=n]
Specify the wineserver persistence delay, i.e. the amount of time that the server will keep running when all client processes have
terminated. This avoids the cost of shutting down and starting again when programs are launched in quick succession. The timeout n
is in seconds, the default value is 3 seconds. If n is not specified, the server stays around forever.
-v, --version
Display version information and exit.
-w, --wait
Wait until the currently running wineserver terminates.
ENVIRONMENT VARIABLES
WINEPREFIX
If set, the content of this variable is taken as the name of the directory where wineserver stores its data (the default is
$HOME/.wine). All wine processes using the same wineserver (i.e.: same user) share certain things like registry, shared memory and
kernel objects. By setting WINEPREFIX to different values for different Wine processes, it is possible to run a number of truly
independent Wine sessions.
WINESERVER
Specifies the path and name of the wineserver binary that will be launched automatically by wine. If not set, wine will try to load
/usr/bin/wineserver, and if this doesn't exist it will then look for a file named wineserver in the path and in a few other likely
locations.
FILES
~/.wine
Directory containing user specific data managed by wine.
/tmp/.wine-uid
The directory containing the server Unix socket and the lock file. These files are created in a subdirectory generated from the
WINEPREFIX directory device and inode numbers.
AUTHORS
The original author of wineserver is Alexandre Julliard. Many other people have contributed new features and bug fixes. Please check the
file Changelog in the Wine distribution for the complete details.
BUGS
If you find a bug, please submit a bug report at http://bugs.winehq.org. <http://bugs.winehq.org>
AVAILABILITY
wineserver is part of the Wine distribution, which is available through WineHQ, the Wine development headquarters, at
http://www.winehq.org/. <http://www.winehq.org/>
SEE ALSO wine(1).
Wine 1.2-rc6 October 2005 WINESERVER(1)