Sponsored Content
Full Discussion: Linux Desktop OS
Operating Systems Linux Linux Desktop OS Post 302855385 by cjcox on Thursday 19th of September 2013 05:37:12 PM
Old 09-19-2013
Word 2010 running under Linux (openSUSE using Wine)

Image
 

5 More Discussions You Might Find Interesting

1. Linux

Desktop of linux server

Hi, How to get desktop of linux server in windows using putty or any other software (1 Reply)
Discussion started by: manoj.solaris
1 Replies

2. Linux

Best Linux desktop distro

I hate the fact that my first post is this. Anyhow, I've been using Linux distros such as Ubuntu, Fedora, Debian, openSUSE, and a few others for quite some time now. I've never had a problem with any distro, thus saying that they were all good in my opinion. I've been reading a lot on different... (2 Replies)
Discussion started by: Vex
2 Replies

3. What is on Your Mind?

Linux Desktop vs Windows 8

Any comments on this Windows 8 OEM specs may block Linux booting | ITworld (16 Replies)
Discussion started by: jgt
16 Replies

4. Fedora

Build Linux Desktop ?

Hi, Just trying to make a plan as to if this doable or not? Currently in the company all the desktop are Windows, users get MS-Word, some kind of Virus program. and all connected to Windows domain. If I want to do the same thiing on Linux? How would I do that? First I need to create... (3 Replies)
Discussion started by: samnyc
3 Replies

5. Red Hat

VXVM on Linux desktop

I would like to install vmvm on linux for practice My hdd is only 1 & its a intel core i5 processor which i believe is 64 bit.. Has anyone have experience of installing it on desktop ? Or any other advice to learn it ? Thanks (3 Replies)
Discussion started by: heman96
3 Replies
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)
All times are GMT -4. The time now is 02:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy