No such file or directory mac os ��� ���

Question: Q: Mac OS X claims «no such file or directory» for a directory that’s clearly there. Why?

/Library | grep Saved

Saved Application State

/Library/Saved Application State/»

/Library/Saved Application State/: No such file or directory

MacBook Pro, Mac OS X (10.7)

Posted on Aug 14, 2011 2:08 PM

Posted on Aug 14, 2011 2:15 PM

Helpful answers

This format works:

/Library/»Saved Application State»/

Aug 14, 2011 2:14 PM

/Library | grep Saved

Saved Application State

/Library/Saved Application State/»

/Library/Saved Application State/: No such file or directory

You told the shell not to expand the tilde by putting everything in quotes. This is not Windows.

/Library/Saved\ Application\ State

Aug 14, 2011 2:15 PM

There’s more to the conversation

Loading page content

Page content loaded

Very odd. Can you navigate to it in the Finder?

You get the same response when navigating to

Aug 14, 2011 2:15 PM

This format works:

/Library/»Saved Application State»/

Aug 14, 2011 2:14 PM

/Library | grep Saved

Saved Application State

/Library/Saved Application State/»

/Library/Saved Application State/: No such file or directory

You told the shell not to expand the tilde by putting everything in quotes. This is not Windows.

/Library/Saved\ Application\ State

Aug 14, 2011 2:15 PM

Aug 14, 2011 2:15 PM

» is not being expanded by the shell.

try ls «$HOME/Library/Saved Application State/» or ls

/Library/Saved\ Application\ State/

Aug 14, 2011 2:18 PM

Thanks, everyone. Is there a quick way to list all these $ environment variables and see what points where? I know about $PATH and $HOME, but are there any others, what do they do, and can I list them all?

Aug 14, 2011 2:33 PM

One way in Terminal is to enter: env

Aug 14, 2011 3:31 PM

Question: Q: Mac OS X claims «no such file or directory» for a directory that’s clearly there. Why? More Less

Источник

Question: Q: -bash: your: No such file or directory

I see this when I open up Terminal. I an on a Macbook Pro with Sierra. I’m not sure what to do from here. Here is the whole thing:

Last login: Tue Apr 18 09:33:31 on ttys000

-bash: your: No such file or directory

MacBook Pro, macOS Sierra (10.12.4), 15″ display

Posted on Apr 18, 2017 9:52 AM

All replies

Loading page content

Page content loaded

This suggests that some command you have on your .bash_profile is giving an error.

This is a file in your home directory that contains commands that are executed when a bash shell starts.

Copy and paste the following command in a Terminal window and let us know what you get:

Apr 18, 2017 10:52 AM

Hi thanks for responding. This is what I got:

export PATH=$PATH:/Users/ /Library/Android/sdk/platform-tools/

Apr 18, 2017 9:40 PM

Also, not sure why there is a «$» after my user name. My directory shows sfjenn. Or is the $ part of a command a command?

Apr 18, 2017 9:42 PM

I’m guessing somehow your .bashrc file has some incorrect commands in it. Try renaming the file in Finder (you need to show invisible files to see it with Shift+Command+. keyboard shortcut) to something else (for example .bashrc_bad), and then start Terminal.app again. If that works you can then in the Terminal window:

and post the results and we can try and give you some input on what is bad.

Apr 18, 2017 11:36 PM

/.profile or even possibly /etc/profile.

Sorry about that.

Apr 18, 2017 11:39 PM

Hi thanks for responding. This is what I got:

export PATH=$PATH:/Users/ /Library/Android/sdk/platform-tools/

There you have it.

See the word «your» in there? Where it says » » it was supposed to be a placeholder, to be replaced by your short username (i.e., the name that appears next to the home folder in your Finder sidebar), but you left it literally.

The effect of that command (which, of course, is not working as it is) was to allow command line access to some tools for developing for Android. You obviously haven’t been using those, at least not from the command line.

If you don’t care about running stuff for running some sdk for Android from the command line, just delete this file by copying and pasting the following line exactly, to a Terminal window, and pressing enter:

The next time your ran bash (or open a new Terminal window) you won’t see the error anymore.

Источник

Question: Q: «No such file or directory» errors on Time Machine backup volume

I remotely mounted the Time Machine backup volume onto another Mac and was looking around it in a Terminal window and discovered what appeared to be a funny problem. If I «cd» into some folders (but not all) and do a «ls -la» command, I get a lot of «No such file or directory» errors for all the subfolders, but all the files look fine. Yet if I go log onto the Mac that has the backup volume mounted as a local volume, these errors never appear for the exact same location. Even more weird is that if I do «ls -a» everything appears normal on both systems (no error messages anyway).

It appears to be the case that the folders that have the problem are folders that Time Machine has created as «hard links» to other folders which is something that Time Machine does and is only available as of Mac OS X 10.5 and is the secret behind how it avoids using up disk space for files that are the same in the different backups.

I moved the Time Machine disk to the second Mac and mounted the volume locally onto it (the second Mac that was showing the problems), so that now the volume is local to it instead of a remote mounted volume via AFP and the problem goes away, and if I do a remote mount on the first Mac of the Time Machine volume the problem appears on the first Mac system that was OK — so basically by switching the volume the problem switches also on who shows the «no such file or directory» errors.

Because of the way the problem occurs, ie only when the volume is remote mounted, it would appear to be an issue with AFP mounted volumes that contain these «hard links» to folders.

There is utility program written by Amit Singh, the fella who wrote the «Mac OS X Internals» book, called hfsdebug (you can get it from his website if you want — just do a web search for «Mac OS X Internals hfsdebug» if you want to find it ). If you use it to get a little bit more info on what’s going on, it shows a lot of details about one of the problematic folders. Here is what things look like on the first Mac (mac1) with the Time Machine locally mounted:

So you can see from the first few lines of the «ls -a» command, it shows some file/folders but you can’t tell which yet. The next «ls -la» command shows which names are files and folders — that there are some folders (like ACPI) and some files (like A.txt and A9.txt) and all looks normal. And the «hfsdebug» info shows some details of what is really happening in the «Documents» folder, but more about that in a bit.

And here are what a «ls -a» and «ls -al» look like for the same locations on the second Mac (mac2) where the Time Machine volume is remote mounted:

If you look very close a hint as to what is going on is obvious — the inode for the Documents folder is 152 on the local mounted case (the first set of code above for mac1), and it’s 728505 in the remote mounted case for mac2. So it appears that these «hard links» to folders have an extra level of folder that is hidden from you and that AFP fails to take into account, and that is what the «hfsdebug» shows even better as you can clearly see the REAL location of the Documents folder is in something called «/.HFS+ Private Directory Data%000d/dir_135» that is not even visible to the shell. And if you look closely in the remote mac2 case, when I did the «cd Documents» I don’t go into the inode 135, but into the inode 728505 (look close at the «.» entry for the «ls -la» commands on both mac1 and mac2) which is the REAL problem, but have no idea how to get AFP to follow the extra level of indirection.

Anyone have any ideas how to fix this so that «ls -l» commands don’t generate these «no such file or folder» messages?

I am guessing that the issue is really something to do with AFP (Apple File Protocol) mounted remote volumes. The TimeMachine example is something that I used as an example that anyone could verify the problem. The real problem for me has nothing to do with Time Machine, but has to do with some hard links to folders that I created on another file system totally separate from the Time Machine volume. They exhibit the same problem as these Time Machine created folders, so am pretty sure the problem has nothing to do with how I created hard links to folders which is not doable normally without writing a super simple little 10 line program using the link() system call — do a «man 2 link» if you are curious how it works.

I’m well aware of the issues and the conditions when they can and can’t be used and the potential hazards. I have an issue in which they are the best way to solve a problem. And after the problem was solved, is when I noticed this issue that appears to be a by-product of using them.

Do not try these hard links to folders on your own without knowing what they’re for and how to use them and not use them. They can cause real problems if not used correctly. So if you decide to try them out and you loose some files or your entire drive, don’t say I didn’t warn you first.

Источник

[catalina] after workaround for «idevice_id» run returns ProcessException: ProcessException: No such file or directory #44406

Comments

cfchris commented Nov 8, 2019

Mac updated to Catalina. Ended up with a bunch of permission errors with «idevice_id» etc. Think I got those fixed. But, now I just can’t flutter run from terminal or VS Code.

command

exception

ProcessException: ProcessException: No such file or directory
Command: /usr/local/bin/pod install —verbose

flutter doctor

The text was updated successfully, but these errors were encountered:

iapicca commented Nov 8, 2019 •

Hi @cfchris
did you follow this workaround to fix the idevice_id issue?
Is it the whole log?
thank you

truonghoangduy commented Nov 8, 2019 •

If you has an opened dialog saying somethings about security.

I did a video how to fix it it on YouTube here the link https://youtu.be/L98Y0UT8wuQ

cfchris commented Nov 8, 2019

Hi @cfchris
did you follow this workaround to fix the idevice_id issue?
Is it the whole log?
thank you

I have followed the workaround. And that is the whole log. I just repeated the steps of the workaround and then did flutter run again. Here is what I get in the terminal (which points to a log record like the on I submitted).

cfchris commented Nov 8, 2019

I am going to attempt to delete flutter, and re-install. If that doesn’t fix it, I will attempt to delete and re-clone our repository (for the app).

cfchris commented Nov 8, 2019 •

OK. After re-installing flutter (rm -rf && unzip), and running flutter doctor , I got the security prompts again. So, I cancelled and ran the attribute update fix. Then, I ran flutter doctor and got a more helpful error.

So, then I ran sudo gem install cocoapods . That went fine. So, I tried flutter run again. That failed. But, I just needed to run flutter pub get .

And now finally, I can run the app again. Hope this info helps someone else that get’s stuck.

Источник

macOS Catalina bad interpreter: No such file or directory #15460

Comments

duanhjlt commented Oct 9, 2019 •

I installed Catalina, but i got error when i run fastlane.

The text was updated successfully, but these errors were encountered:

fastlane-bot commented Oct 9, 2019

It seems like you have not included the output of fastlane env
To make it easier for us help you resolve this issue, please update the issue to include the output of fastlane env 👍

jcharr1 commented Oct 9, 2019

I had this issue after upgrading to Catalina with several gems. What I had to do is uninstall all my user gems, delete the contents of my user gems directory, and then reinstall the gems. The key was that it wasn’t enough to just uninstall them through gem. I had to manually delete the directory contents too.

T-Jedsada commented Oct 9, 2019 •

alindaj6 commented Oct 9, 2019

@jcharr1 can you tell me what are you doing in detail to make the fastlane working again?
i am really stuck now

jcharr1 commented Oct 9, 2019 •

@alindaj6 how did you install fastlane? Directly with gem or with brew ?

Basically, what you need to do is go into the folder where your gems are installed (GEM_HOME), delete the contents of that folder, and then reinstall fastlane and any other gems you need. That should point the gems to the correct version of Ruby that was updated in Catalina.

jcharr1 commented Oct 9, 2019 •

For example, I have my GEM_HOME setup to be in my user folder (

/.gem) so I can install gems without using sudo . So in my case, what I did was:

1. run gem uninstall -aIx . This should uninstall all your installed gems and their binaries. Though this doesn’t seem to completely get rid of them and it didn’t fix the error for me after reinstalling.
2. So next I went into my gem install directory and deleted the contents of it. For me this is

Источник