9front - general discussion about 9front
 help / color / mirror / Atom feed
From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org
Subject: Re: [9front] File sharing with Windows
Date: Wed, 22 Jun 2022 04:36:37 -0400	[thread overview]
Message-ID: <35aa07f8-7a3c-9437-3dfc-d1829cecb61c@fjrhome.net> (raw)
In-Reply-To: <4dd8a8cd-4cc4-1d2f-32a2-b6a69eec6f88@riseup.net>

What does the exclamation point at the start of the service file name do?

I don't see that documented in the man page for listen, and looking at 
/rc/bin/service on my own system, it is present on more files than not, 
but there are a few which do not have it.

When I try to telnet to one of those ports, the ones with the 
exclamation points do not allow the connection, but the ones without 
them do, which leads me to believe that it is effectively disabling 
those services, so wouldn't !tcp445 need to be renamed to remove the 
exclamation point for this to work?


On 6/22/22 3:44 AM, mkf9 wrote:
> stefncb@gmail.com wrote:
>>
>> I changed /rc/bin/service/!tcp445 to:
>>
>>     #!/bin/rc
>>     exec /bin/ip/cifsd -f /sys/log/cifsd.debug -w WORKGROUP -o 
>> trspaces $*
>>
>> (The only thing I thought made sense to change was the workgroup, it 
>> now matches the Windows PC).
>>
>> And then ran aux/listen. Am I supposed to find a new network share on 
>> the Windows PC now? I don't.
>>
>> Jacob mentioned SMBv3 support, but going through the Windows features 
>> I could enable SMBv1/CIFS support, which didn't help.
>>
>> I thought I should check the debug log - /sys/log/cifsd.debug doesn't 
>> even exist. How do I check if the service is actually running?
>>
>
> it doesn't appear on auto discovery,
> add it manually (map a network drive).
>


  parent reply	other threads:[~2022-06-22  8:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 12:52 stefncb
2022-06-21 16:02 ` Jacob Moody
2022-06-21 15:20   ` stefncb
2022-06-21 18:34     ` mkf9
2022-06-21 18:37       ` Jacob Moody
2022-06-22  4:14       ` stefncb
2022-06-22  7:44         ` mkf9
2022-06-22  5:26           ` stefncb
2022-06-22  8:36           ` Frank D. Engel, Jr. [this message]
2022-06-22  5:51             ` stefncb
2022-06-22  9:01               ` Frank D. Engel, Jr.
2022-06-22  9:12                 ` stefncb
2022-06-22 11:38                   ` Steve Simon
2022-06-22 11:43                     ` mkf9
2022-06-22 11:47                       ` Steve Simon
2022-06-22 11:47                     ` stefncb
2022-06-22 14:23                     ` cinap_lenrek
2022-06-22 14:49                       ` Steve Simon
2022-06-22 16:57                         ` sirjofri
2022-06-22 17:42                           ` Marshall Conover
2022-06-22 20:28                             ` Steve Simon
2022-06-21 16:07   ` Marshall Conover
2022-06-21 15:21     ` stefncb

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35aa07f8-7a3c-9437-3dfc-d1829cecb61c@fjrhome.net \
    --to=fde101@fjrhome.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).