2005-03-16 21:26:28

Winserv is an utility that can create an NT service that runs any application. When the application exits, the service becomes stopped. It is also able to manage local and remote NT services that were not created by winserv.

Winserv is used now in ProjectForum and CourseForum as a wrapper for running these applications as NT services.

Download
Register Now. Winserv is both free and open-source, but you may express your interest in the further Winserv development by supporting it with voluntary donation of $20.
Release Notes and Change Log?

The intended audience of Winserv consists of the very different people:

System administrators and power users who need a command-line tool to manage windows NT services, locally or remotely.
Programmers who are going to implement a service in a language like python or ruby; programmers with a UNIX background, who want to implement an NT service but don't have time to learn Windows API or to read MSDN.
TCL programmers and users, familiar with tclsvc or Tcl Dev Kit and with NT services in general; they may need a more powerful tool to implement and manage NT services.

Thus It's almost impossible to provide the documentation suitable for anyone in such different groups. So we encourage you to skip calmly the pieces of documentation that seems unclear. Usually it means that the piece is not for you and you don't need to understand it.

Winserv can be used as a command-line utility to configure, control, view status of any NT service, whether it is winserv-based or not. Winserv can interact with a remote machine's service control manager. When you use winserv from a command prompt, just prepend \\Machine\ to the service name if you want to operate with remote service:
Winserv status \\MyServer\alerter
The service name that winserv requires is not the display name of the service, but rather the internal unique name.

Winserv is designed with scripting languages in mind, TCL in particular. It can forward SCM control requests to the application in different ways, enabling you to do any cleanup on stop and to implement “paused” service state.

Winserv contains a little TCL package that lets you use it as a drop-in replacement for tclsvc.

Winserv command-line reference?
Winserv internals?
TCL-specific notes?
Using winserv with Win32 console programs?

Licensing and Redistribution?

2005-02-22 09:34:30

edited by AntonKovalenko

2005-02-22 09:34:04

edited by AntonKovalenko

2004-11-07 02:28:53

edited by AntonKovalenko

2004-11-07 01:50:25

edited by AntonKovalenko

2004-11-07 01:12:17

edited by AntonKovalenko

2004-11-06 20:05:41

edited by AntonKovalenko

2004-11-06 20:03:28

edited by AntonKovalenko

2004-11-06 19:54:59

edited by AntonKovalenko

2004-11-06 19:54:33

edited by AntonKovalenko

2004-11-06 19:54:09

edited by AntonKovalenko

2004-11-06 19:52:43

edited by AntonKovalenko

2004-11-06 19:02:47

edited by AntonKovalenko

2004-11-06 19:00:42

edited by AntonKovalenko

2004-11-06 17:13:57

edited by AntonKovalenko

2004-11-06 17:13:23

edited by AntonKovalenko

2004-11-06 17:08:54

edited by AntonKovalenko

2004-11-06 17:08:23

edited by AntonKovalenko

2004-11-06 17:06:26

edited by AntonKovalenko

2004-11-06 17:06:10

edited by AntonKovalenko

Sw4me - Winserv

2005-03-16 21:26:28

2005-02-22 09:34:30

2005-02-22 09:34:04

2004-11-07 02:28:53

2004-11-07 01:50:25

2004-11-07 01:12:17

2004-11-06 20:05:41

2004-11-06 20:03:28

2004-11-06 19:54:59

2004-11-06 19:54:33

2004-11-06 19:54:09

2004-11-06 19:52:43

2004-11-06 19:02:47

2004-11-06 19:00:42

2004-11-06 17:13:57

2004-11-06 17:13:23

2004-11-06 17:08:54

2004-11-06 17:08:23

2004-11-06 17:06:26

2004-11-06 17:06:10