FractalCZ Posted August 20, 2023 Share Posted August 20, 2023 13 hours ago, darwinmac said: That’s correct. To have the tnfsd daemon run automatically on restart, I think you’ll need to add it to launchd. I haven’t had the time to make it work yet. Bob C At this time, it's not necessary as I don't switch my atari on on daily basis. Quote Link to comment Share on other sites More sharing options...
FractalCZ Posted August 22, 2023 Share Posted August 22, 2023 OK, getting somewhere. The Fujinet and the server are obviously seeing each other, but I have no folder listing at all. At the atari side, it just jumps to the "wifi overview" screen. On the Mac side, I have this output. What am I missing? Quote Link to comment Share on other sites More sharing options...
FractalCZ Posted August 23, 2023 Share Posted August 23, 2023 OMG - found it myself. I forgot "~" in front of my desired path. It works like a charm. 1 Quote Link to comment Share on other sites More sharing options...
darwinmac Posted August 26, 2023 Share Posted August 26, 2023 (edited) Finally, I had time to pull my hair out and get the tnfsd daemon working on launchd. That makes it so tnfsd is always running if my Mac is turned on and logged in to my user account. If my Mac is turned on, it's always logged into my user account. If you wanted tnfsd running on any account, that would be a LaunchDaemon which I didn't set up. That's left as an exercise for the reader. Anyway, I'll include my plist and the shell script I wrote tagged as spoilers so those of you who don't care won't have to scroll past it. It felt good to finally get this working. Thom has instructions for Windows users on how to get tnfsd running on boot, but nothing for macOS since I don't think he runs that OS. Bob C Spoiler Plist file created in ~/Library/LaunchAgents saved as com.bobc.tnfsd.plist <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.bobc.tnfsd</string> <key>ProgramArguments</key> <array> <string>/opt/local/tnfsd.sh</string> </array> <key>RunAtLoad</key> <true/> </dict> </plist> Shell script created with filename of tnfsd.sh saved in /opt/local directory: /opt/local/tnfsd /Users/bobc/Documents/Altirra /Users/bobc/Documents/Altirra is where I keep my Atari 8-bit files for Fujinet to browse. I could've written this as ~/Documents/Altirra, but I was trying to eliminate every possible failure point. From my reading, it appears that plist files run in ~/Library/LaunchAgents run as that logged in user. If that's the case, then "~/" would've worked. com.bobc.tnfsd.plist tnfsd.sh Edited August 26, 2023 by darwinmac 1 Quote Link to comment Share on other sites More sharing options...
darwinmac Posted August 27, 2023 Share Posted August 27, 2023 For anyone who may care, here's an updated launchd plist file that doesn't require the extra script. I couldn't get the "~/" shorthand to work. I don't remember if that's a limitation in tnfsd or simply I did wrong in the plist file. The "ps" command showed the correct parameter, but Fujinet said it couldn't mount the host until I wrote out /Users/bobc/Documents/Altirra in the plist file (where my 8-bit files are stored on my Mac). Hopefully, this will help someone who's trying to automatically boot tnfsd on their Mac and is having problems. If you're running an older version of macOS, it may still be using crontab in order to automatically run executables on bootup. Bob C com.bobc.tnfsd.plist 3 1 Quote Link to comment Share on other sites More sharing options...
FractalCZ Posted August 30, 2023 Share Posted August 30, 2023 It's just a relief being looking at my two computers 40 years apart chatting with each other 1 Quote Link to comment Share on other sites More sharing options...
sideburn Posted January 2 Share Posted January 2 (edited) If you want your server to launch and run in the background on login, make a .plist file in ~/library/LaunchAgents edit: oops I see this has already been mentioned… Edited January 2 by sideburn Quote Link to comment Share on other sites More sharing options...
magnusfalkirk Posted March 12 Share Posted March 12 (edited) On the host list page for fujinet what do I need to name my MacBook pro that I have the tfns server configured on? Just changed my Internet provider and now the Fujinet plugged into my //c+ connects to the Internet. I have the path set using Terminal, and it is currently running, just need to know how to access it from the Apple //c+. I've tried using the name of the MacBook, the path that the Apple II folder is in. Neither work, it tries to open it but says can't open the directory. Help Please! I'm running MacOS Big Sur on an Intel Mac. Edited March 12 by magnusfalkirk Quote Link to comment Share on other sites More sharing options...
mozzwald Posted March 12 Share Posted March 12 13 minutes ago, magnusfalkirk said: On the host list page for fujinet what do I need to name my MacBook pro that I have the tfns server configured on? Just changed my Internet provider and now the Fujinet plugged into my //c+ connects to the Internet. I have the path set using Terminal, and it is currently running, just need to know how to access it from the Apple //c+. I've tried using the name of the MacBook, the path that the Apple II folder is in. Neither work, it tries to open it but says can't open the directory. Help Please! I'm running MacOS Big Sur on an Intel Mac. if your network doesn't support mDNS or it's not working, you can always put the IP address of your TNFS server instead of a name Quote Link to comment Share on other sites More sharing options...
magnusfalkirk Posted March 12 Share Posted March 12 I'll give that a try, thanks Quote Link to comment Share on other sites More sharing options...
magnusfalkirk Posted March 12 Share Posted March 12 Well crap. Tried your suggestion and it's still saying 'could not open directory' Quote Link to comment Share on other sites More sharing options...
tschak909 Posted March 12 Share Posted March 12 16 hours ago, magnusfalkirk said: Well crap. Tried your suggestion and it's still saying 'could not open directory' Is there a significant delay before it states that it can't open the directory? It can possibly be a firewall on your Mac preventing connection to the tnfs server. Quote Link to comment Share on other sites More sharing options...
magnusfalkirk Posted March 12 Share Posted March 12 no, there is no delay, it's immediate Quote Link to comment Share on other sites More sharing options...
tschak909 Posted March 12 Share Posted March 12 Can you paste output from the flasher's debug monitor, as the error happens? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.