Sponsored Content
Full Discussion: Server security
Top Forums UNIX for Dummies Questions & Answers Server security Post 302267200 by cbkihong on Thursday 11th of December 2008 09:02:25 PM
Old 12-11-2008
Quote:
Originally Posted by daydreamer
Is a virus scanner needed at all?
I don't run one. I'm not sure but I think many viruses nowadays are either Windows executables (.COM, .BAT, .EXE) or scripts (.JS/.VBS). A typical Unix-based environment does not directly support execution of these (though you may be able to do so with selected emulators say Wine or specific libraries). Of course, still, you should be careful with opening downloaded files. Say with mounted Windows shares you may still be spreading viruses to other Windows systems even if they don't harm yours.
 

4 More Discussions You Might Find Interesting

1. Cybersecurity

permissions and security with windows 2000 server

I setup a Windows 2000 Server so that a G4 could access one specific folder. The only way this contact could take place between the two operating systems is with Maclan. I have not installed it with the PCmaclan currently, I have only been reading about it. Can someone assist me with this... (0 Replies)
Discussion started by: pmoncriffe
0 Replies

2. UNIX for Advanced & Expert Users

Are there many UNIX server security enhanced products?

for sco, hp, or AIX...... anyway, how can I secure the UNIX system. I knew that CA has it's products for securing the UNIX server system. Please tell me more about other vender, and their products thxs! (0 Replies)
Discussion started by: brookwk
0 Replies

3. Red Hat

Zimbra Mail Server Security Issue

Hello, I have issue with my Zimbra Mail Server 6.0.7. In that i have configured HTTPS for client login and for whole session. but it stills communicate in http based authentication. due to that some sniffing software are easily sniffing details. So how do i configure completely HTTPS in... (3 Replies)
Discussion started by: Chintanghanti
3 Replies

4. Cybersecurity

Two Factor Authentication – Best for the UNIX/Linux Server Security

The UNIX/Linux server security is challenging because these servers are at a risk of getting compromised at any point of time by the attackers. In today's enterprise environment, the UNIX and Linux servers are growing popular. With their increased popularity, these servers have become the primary... (1 Reply)
Discussion started by: reve-secure
1 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 03:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy