Hello, Thank you for such expeditious response to this matter, very appreciated. I'm also in agreement with you that this isn't 100% a bug, but rather a feature lacking in this software. So I'm not sure this should be reported as an upstream bug, but rather a feature request, as you stated.
Let me know what you think the next best course of action should be. I took a look at the workaround you posted, It's ok, but for example the project that my team is working on is ultimately creating an environment that's goal is to test 100 clients operating at the same time (20 Clients/Screen sessions per host) this would be tedious trying to setup individual scripts/configuration files, as opposed to using the " | tee <filename> " method I've implemented for the time being. This is why I'm trying to find the best avenue for having this addressed, as the improvement that needs to be made is simply having the screen package be able to do: screen -L /path/to/logfile this would make life so much simpler :) I'm also not familiar with filing upstream bugs/feature requests, etc. This is my first Ubuntu bug filing experience with this matter. Any guidance would be appreciated. Thank you ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714182 Title: Cannot specify customized filename for output logging (-L flag) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/screen/+bug/1714182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
