search

qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
26.62k stars 3.86k forks source link

Provide qbittorrent-nox for Windows #8664

Open robross0606 opened 6 years ago

robross0606 commented 6 years ago

Please provide the following information

qBittorrent version and Operating System

4.0.4 Windows

What is the problem

Unlike on Linux, there is no qBittorrent-nox option for running a lighter daemon version on Windows with nothing but a WebUI. Is it possible to compile this? Why is it not supplied in the release?

What is the expected behavior

A "headless" version such as qBittorrent-nox.exe would be supplied in the release installer.

evansan commented 6 years ago

qBittorrent-nox for Linux is compiled by their package teams, not by qBittorrent team. You have to compile it yourself on Windows.

WolfganP commented 6 years ago

qBittorrent-nox is intended for headless systems (mostly command line Linux w/o GUI system installed). MS Windows is inherently a graphical system, so a qb-nox windows version doesn't make much sense. You can have the same functionality running the standard qB for windows minimized and just using the WebUI.

robross0606 commented 6 years ago

With all due respect, "effective functionality" and "minimal overhead" are not the same thing.

WolfganP commented 6 years ago

With all due respect, "effective functionality" and "minimal overhead" are not the same thing.

Minimal overhead... in Windows?!? :-)

seeme-o commented 5 years ago

@WolfganP do you know anything of qBittorrent-nox? It is not a cli, but http backend. In fact you can't even use qBittorrent-nox over commandline without using curl or similar which no no easy task...

WolfganP commented 5 years ago

@need-sleep yep, I know something about it... running a qb-nox on a headless RasPi2 for several years, all remotely managed via alt-webUI, built from master every week or so.

jcoryatjr commented 4 years ago

qBittorrent-nox is intended for headless systems (mostly command line Linux w/o GUI system installed). MS Windows is inherently a graphical system, so a qb-nox windows version doesn't make much sense. You can have the same functionality running the standard qB for windows minimized and just using the WebUI.

Window Server Core and Nano are headless OS's...

robross0606 commented 4 years ago

Not everything in Windows is inherently graphical. Almost every service running in Windows is not graphical.

Orhideous commented 2 years ago

It would be nice to provide such a distribution, at least start building it on CI, as has already been done for Ubuntu.

Pentaphon commented 1 year ago

Transmission 4,x allows you to install the daemon-only as a Windows service and I think qBitTorrent could easily do the same on Windows.

DNS commented 1 year ago

There's no need to use qbittorrent-nox on Windows. You can use qbittorrent.exe and achieve the same thing. If you use ssh to connect to this machine, and using PowerShell as default terminal, this is how to do it:

winget install GNU.Nano nano $env:APPDATA\qBittorrent\qBittorrent.ini

WebUI\Enabled=true

And then run qbittorrent.exe as daemon Start-Process 'C:\Program Files\qBittorrent\qbittorrent.exe' -WindowStyle Hidden

Then open your Web Browser and access it from http://IPADDRESS:8080/

To stop the qbittorrent.exe Get-Process qbittorrent | Stop-Process Or exit from WebUI: File > Exit qBittorrent

This has the same effect as running qbittorrent-nox on Linux/FreeBSD.

RAM usage: qbittorrent.exe on Windows use 30 MB RAM. qbittorrent-nox on FreeBSD use 29 MB RAM.

Pentaphon commented 1 year ago

There's no need to use qbittorrent-nox on Windows. You can use qbittorrent.exe and achieve the same thing. If you use ssh to connect to this machine, and using PowerShell as default terminal, this is how to do it:

That's certainly a way to do it, but it's not the user-friendly way to do it which is what people really want since qBittorrent is a user-friendly torrent client. The point is to not have to install the full qBittorrent client at all and install install -nox as a service by itself.

Take the example of Transmission 4.0.3:

1) Run the installer 2) Select transmission-daemon and (optionally) the WebUI and install 3) You now have transmission-daemon running as a Windows service whenever your Windows PC is on and you can connect to it via localhost:9091 and change the settings as you wish.

I strongly suspect this is what robross0606 wants with qbittorrent-nox and I think it is worth pursuing. Not everybody wants the full client on their desktop, even on a Windows machine. Many people just want a headless torrent client running in the background on their PC, where they can connect to it from any number of UIs both locally and remotely if needed.

For anybody who says Windows doesn't need this: just because we are talking about Windows doesn't mean that nobody wants a headless client. There's been more Linux-friendly software on Windows in the past decade than ever and since Windows is still the most used OS, so there's a never been a better time for making qBittorrent-nox work as a Windows service. I hope somebody out there feels the same and is able to make it work on Windows.

DNS commented 1 year ago

Clearly you're not a programmer.

"qbittorrent-nox" (-nox -> No X) is needed on Linux because "qbittorrent" always need X to run on Linux. "qbittorrent.exe" doesn't need X to run on Windows. And there's no such thing as X in Windows, unless you use Cygwin. It doesn't matter if you remove Qt dependency on Windows, because the end result will be the same. It achieve the same thing & about the same RAM usage.

So asking for -nox in Windows is very dumb because Windows doesn't have X in the first place. It's feel like begging for something nonexistent.

What you really want is to simplify the installation of "qbittorrent" as "Windows Service", not qbittorrent-nox. This can be done now just by writing a simple PowerShell script

So my suggestion is to create another issue, ask the developers to make "install qbittorrent as Windows Service". Which is pretty much redundant, because qBittorrent already have the option to start when Windows startup.

glassez commented 1 year ago

@DNS nox (aka no X) is a legacy name. It just refers to no GUI, i.e. the variant without any support for GUI (any GUI related code is excluded from executable).

DNS commented 1 year ago

@glassez as I write earlier, stripping the GUI/Qt from the codebase won't make any difference in RAM consumption, it doesn't make lighter client. The end result will be the same, it achieve the same thing with less functionality (no Qt, only Web UI).

Right now on Windows (GUI), qbittorrent.exe only use 28 MB RAM (7 torrents download, 46 completed, 0 seed). While on FreeBSD (no GUI), qbittorrent-nox consume 137 MB RAM (1 torrent download, 6 completed, 0 seed).

Also qbittorrent.exe can be run as daemon (no GUI, headless), or minimized in system tray.

If you really want light client, use the original utorrent/bittorrent client.

Pentaphon commented 1 year ago

stripping the GUI/Qt from the codebase won't make any difference in RAM consumption, it doesn't make lighter client. The end result will be the same, it achieve the same thing with less functionality (no Qt, only Web UI).

You don't know that for sure until it's actually done for Windows the way OP wants in a user-friendly manner as Transmission has done. Until you have a separate, stripped-down Windows qBittorrent-daemon and can test it alongside qBittorrent desktop client, you simply can't say they are 100% the same in terms of resource usage.

So asking for -nox in Windows is very dumb because Windows doesn't have X in the first place. It's feel like begging for something nonexistent.

That is completely irrelevant to the issue. The OP wants a simple daemon to be installed by the installer. X isn't even an issue here and you need to drop the semantics.

Also qbittorrent.exe can be run as daemon (no GUI, headless), or minimized in system tray.

Not in a user-friendly way such as Transmission 4.0.3 has achieved.

What you really want is to simplify the installation of "qbittorrent" as "Windows Service", not qbittorrent-nox. This can be done now just by writing a simple PowerShell script

Again, not user-friendly.

So my suggestion is to create another issue, ask the developers to make "install qbittorrent as Windows Service". Which is pretty much redundant, because qBittorrent already have the option to start when Windows startup.

Again, the -nox name doesn't matter. The devs know what we want. We just have to change the title of this issue, not create another one.

You're talking in circles now because you're hung up on the -nox thing. We just want qBitorrent-daemon available to Windows in a user-friendly manner. @robross0606 can just change the title of this issue to "install qbittorrent-daemon as Windows Service with Installer" and your qualms will be put to rest.

DNS commented 1 year ago

Windows qBittorrent-daemon and can test it alongside qBittorrent desktop client, you simply can't say they are 100% the same in terms of resource usage.

Excessive RAM usage is not caused by GUI or non-GUI. It is caused by disk cache (which is actually a good thing).

If you don't like the excessive RAM usage, you can set it manually in: Tools > Options > Advanced > Disk Cache.

Not in a user-friendly way such as Transmission 4.0.3 has achieved.

Then make pull request. Begging alone will take you nowhere.

Pentaphon commented 1 year ago

Excessive RAM usage is not caused by GUI or non-GUI. It is caused by disk cache (which is actually a good thing).

It's not just RAM usage. Until you can test a stripped-down qBittorrent-daemon alongside the desktop client, you are making assumptions.

Then make pull request. Begging alone will take you nowhere.

Not everybody codes here. Assuming this is silly.

Your comments are going nowhere. This is what people want. Let them request it.

DNS commented 1 year ago

@Pentaphon Get lost. Troll elsewhere.

expressrussian commented 9 months ago

There's no need to use qbittorrent-nox on Windows. You can use qbittorrent.exe and achieve the same thing. If you use ssh to connect to this machine, and using PowerShell as default terminal, this is how to do it:

THERE IS THE NEED to have a SERVICE-ONLY mode on WIndows WITHOUT HAVING TO LOG IN LOCALLY! So, no hidden windows because without login there are NO windows. I need to use it on my remote WIndows server, i do NOT use QBittorrent on my desktop. On the remote windows server there is no need for GUI nor command line. Only config file maybe. The MAIN PURPOSE of this whole thread is to display a NEED to have a headless windows service which provides only WEB interface, which we can access remotely and by many different users and 24/7. This may be a setup option of some kind. This should not be super-hard to implement. Thanks

Pentaphon commented 4 months ago

nox (aka no X) is a legacy name. It just refers to no GUI, i.e. the variant without any support for GUI (any GUI related code is excluded from executable).

Yes. People really are just asking for a "qBittorrent-daemon" similar to "Transmission-daemon" which comes with Transmission and can be installed as a Windows service along with the WebUI or no WebUI at all. Here is a screenshot of how Transmission installs their daemon. If qBittorrent could do the same thing with their installer, it would make qBittorrent even more useful to people that don't need a desktop client running 24/7.

image