Scp ошибка not a regular file

A regular file is a file that isn’t a directory or more exotic kinds of “special” files such as named pipes, devices, sockets, doors, etc. Symbolic links are not regular files either, but they behave like their target when it an application is accessing the content of the file.

You passed root@IP: as the source of the copy and /path/to/picture.jpg as the destination. The source is the home directory of the user root on the machine IP. This is useful as a destination, but not as a source. What you typed required to copy a directory onto a file; scp cannot copy a directory unless you ask for a recursive copy with the -r option (and it would refuse to overwrite an existing file with a directory even with -r, but it would quietly overwrite a regular file if the source was a regular file).

If /path/to/picture.jpg is the path on the remote machine of the file you want to copy, you need to stick the file name to the host specification. It’s the colon : that separates the host name from the remote path. You’ll need to specify a destination as well.

scp root@IP:/path/to/picture.jpg /some/destination

If you want to copy the local file /path/to/picture.jpg to the remote host, you need to swap the arguments. Unix copy commands put the source(s) first and the destination last.

scp /path/to/picture.jpg root@IP:

If you want to copy the remote file /path/to/picture.jpg to the same location locally, you need to repeat the path. You can have your shell does the work of repeating for you (less typing, less readability).

scp root@IP:/path/to/picture.jpg /path/to/picture.jpg
scp {root@IP:,}/path/to/picture.jpg

Checking out why the SFTP ‘get’ is throwing the error not a regular file?

The answer is quite simple, add the SFTP option flag to transfer non-regular files.

At Bobcares, we get many requests to fix SFTP errors, as a part of our Server Management Services.

Today, let’s have a look into this SFTP error. We will also see how our Support Engineers fix this.

A snapshot on SFTP get and regular file

Before getting into the error, let’s familiarize what is SFTP.

SFTP aka Secure File Transfer Protocol ensures secure data transfer over SSH. Hence this is otherwise known as SSH File Transfer Protocol.

SFTP use get command to transfer remote files to a local system. For transferring regular files, we use a simple get command. But in case of non-regular files, we need to add option flags to the command.

But what are regular and non-regular files in Linux?

Files like text files, images, binary files, etc are regular files. All others are non-regular files. That is directories, symbolic links, etc. So, improper commands can end up in SFTP get errors. Let’s check out the below instance.

How we fix the error SFTP get ‘not a regular file’?

Recently, one of our customers approached us with an SFTP error. Our Support Engineers checked the error. The customer tried the get operation using the command,

get <directory-name>

And he got the error message,

Cannot download non-regular file: <filename>

The reason was clear, the command usage missed an important flag. That is, for transferring non-regular files or directories, we need to add -r flag. Where -r indicates recursive action.

Hence our Support Engineers corrected the code to,

get -r <directory-name>

And this fixed the error.

Alternatives to SFTP

SCP allows secure copying of files and directories between remote hosts. It relays on SSH to transfer data. The command to transfer file is,

scp username@hostname:/path/to/file /path/to/new/file

Similarly, for remote transfer of file, we use rsync. Rsync allows both remote and local file transfers securely.

[Still having trouble in transferring files remotely? – We’ll help you.]

Conclusion

In short, SFTP get not a regular file is an error message which indicates an incomplete command usage. So, either transfer the file recursively or use alternatives like SCP or rsync. Today, we saw how our Support Engineers help customer transfer files remotely.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

scp gives «not a regular file»

I have a problem when using scp on Linux, it says «not a regular file». I looked at other questions/answers about that, but I can’t find out what’s wrong. I wrote:

Do you understand what’s wrong?

8 Answers 8

I just tested this and found at least 3 situations in which scp will return not a regular file :

«/home/pictures/file.fits» must name an actual filesystem object on the remote server. If it didn’t, scp would have given a different error message.

I see that FITS is an image format. I suppose «/home/pictures/file.fits» is the name of a directory on the remote server, containing FITS files or something like that.

One way this error can occur is if you have a space before the first path like below:

To fix, just take the space out:

simple steps you need to follow

It is possible that you are working with a directory/folder.

If this is the case, here is what you want to do:

First, compress the folder. By running the command:

Then use the scp command normally to copy the file to your destination:

scp path/to/name_of_folder.zip server:localhost:/path/to/name_of_folder.zip

Enter your password if it prompts you for one.

Unzip the name_of_folder.zip with this command:

unzip name_of_folder.zip

That is it, you now have your folder in the destination system. By the way, this is for zip compression.

NOTE: If you are on Mac OS and you don’t want to see resource files such as _MACOSX, you may run:

Meaning the above command should be used instead of that in step 1 above.

Источник

I have a namespace package with folder structure as: CompanyNameDepartmentNameSubDepartmentNamePkgName

Python 3.3 onwards supports namespace packages so I have not place the __init__.py files in the following folders:

When I try to build the sdist, using the following commands:

I get the following error:

I have the task setup as part of azure devops pipeline’s command line task and have set ‘Fail on standard error’ to true. The pipeline fails due to the above error.

1 Answer 1

Though Package init file not found (or not a regular file) is more like a warning than an error locally, it will cause the build pipeline to fail if you set Fail on standard error to true when using VSTS.

VSTS with Fail on standard error to default false:

VSTS with Fail on standard error to true:

1.For this, you can choose to turn-off the option( Fail on standard error ) cause the python namespace package can be generated successfully though that message occurs. So in this situation, I think you can suppress that message.

2.Also, another direction is to resolve the message when generating the package. Since the cause of the message has something to do with your definitions in your setup.py file, you should use setuptools.find_namespace_packages() like this document suggests.

Because mynamespace doesn’t contain an init.py, setuptools.find_packages() won’t find the sub-package. You must use setuptools.find_namespace_packages() instead or explicitly list all packages in your setup.py.

In addition: It’s not that recommended to remove all __init__.py files in packages, check this detailed description from AndreasLukas: If you want to run a particular initialization script when the package or any of its modules or sub-packages are imported, you still require an init.py file.

Источник

List only regular files (but not directories) in current directory

but these do not strike me as being overly elegant. Is there a nice short way to list only the regular files (I don’t care about devices, pipes, etc.) but not the sub-directories of the current directory? Listing symbolic links as well would be a plus, but is not a necessity.

9 Answers 9

With zsh and Glob Qualifiers you can easily express it directly, e.g:

will either only return the list of regular files or an error depending on your configuration.

For the non-directories:

(will include symlinks (including to directories), named pipes, devices, sockets, doors. )

for regular files and symlinks to regular files.

for non-directories and no symlinks to directories either.

To list regular files only:

With symbolic links (to any type of file) included:

Debian/Ubuntu

Print the names of the all matching files (including links):

With absolute paths:

Print the names of all files in /etc that start with p and end with d :

ls has no option to do that, but one of the nice things about unix & linux is that long-winded and inelegant pipelines can easily be turned into a shell script, function, or alias. and these can, in turn, be used in pipelines just like any other program.

Источник

File types In Linux/Unix explained in detail.

“ How many types of files are there in Linux/Unix and what are they? ” This is a common question to every person who starts to learn Linux. O.K, why is it that much important to know file types?

Answer: This is because Linux considers every thing as a file. When ever you start working on Linux/Unix box you have to deal with different file types(linux/unix) to effectively manage them

How many types of file are there in Linux/Unix?

By default Unix have only 3 types of files. They are..

Special files(This category is having 5 sub types in it.)

Here are those files type.

For your information there is one more file type called door file(D) which is present in Sun Solaris as mention earlier. A door is a special file for inter-process communication between a client and server (so total 8 types in Unix machines). We will learn about different types of files as below sequence for every file type.

Regular file type Explained in Linux

How to create regular files in Linux/Unix?
Ans: Use touch/vi command and redirection operators etc.

How can we list regular files?

Example listing of regular files :

Directory file type explained in Linux/Unix

These type of files contains regular files/folders/special files stored on a physical device. And this type of files will be in blue in color with link greater than or equal 2.

Example listing of directories.

How to create them?
Ans : Use mkdir command

Block file type in Linux

These files are hardware files most of them are present in /dev.

How to create them?
Ans : Use fdisk command or create virtual partition.

How can we list them in my present working directory?

Example listing of Block files(for you to see these file, they are located in /dev).

Character device files in Linux

Provides a serial stream of input or output.Your terminals are classic example for this type of files.

How can we list character files in my present working directory?

Example listing of character files(located in /dev)

Pipe files in Linux/Unix

The other name of pipe is a “named” pipe, which is sometimes called a FIFO. FIFO stands for “First In, First Out” and refers to the property that the order of bytes going in is the same coming out. The “name” of a named pipe is actually a file name within the file system.

How to create them?
Ans: Use mkfifo command.

How can we list character files in my present working directory?

Example listing of pipe files

symbolic link files in Linux

These are linked files to other files. They are either Directory/Regular File. The inode number for this file and its parent files are same. There are two types of link files available in Linux/Unix ie soft and hard link.

How to create them?
Ans : use ln command

Socket files in Linux

A socket file is used to pass information between applications for communication purpose

How to create them?
Ans : You can create a socket file using socket() system call available under

Example in C programming

You can refer to this socket file using the sockfd. This is same as the file descriptor, and you can use read(), write() system calls to read and write from the socket.

How can we list Socket files in my present working directory?

Example listing of socket files.

srw-rw-rw- 1 root root 0 2010-02-15 09:35 /dev/log

Источник

So I have two main questions:

This seems wrong for me. Please I need your help to understand what is going here.

3 Answers 3

So what is the sticky bit?

A sticky bit is a permission bit that is set on a directory that allows only the owner of the file within that directory, the owner of the directory or the root user to delete or rename the file. No other user has the needed privileges to delete the file created by some other user.

This is a security measure to avoid deletion of critical folders and their content (sub-directories and files), though other users have full permissions.

Why does /tmp have the t sticky bit?

The /tmp directory can be used by different Linux users to create temporary files. Now, what if an user deletes/rename a file created by some other user in this directory?

Well, to avoid these kind of issues, the concept of sticky bit is used. So for that a 777 is given but preserving the sticky bit is not a bad idea.

How can I setup the sticky bit for a directory?

I’ll set a sticky bit on a directory called test on my Desktop.

Symbolic way ( t represents the sticky bit):

Numerical/octal way (1, sticky bit bit as value 1 in the first position)

Now let us test the results:

To delete/Remove a sticky bit

Now let us test the results:

A Sticky bit is a permission bit that is set on a file or a directory that lets only the owner of the file/directory or the root user to delete or rename the file. No other user is given privileges to delete the file created by some other user.

Sometime it happens that you need Linux directory that can be used by all the users of the Linux system for creating files. Users can create, delete or rename files according to their convenience in this directory.

Now, what if an user accidentally or deliberately deletes (or rename) a file created by some other user in this directory?

Well, to avoid these kind of issues, the concept of sticky bit is used. Since /tmp is used for this purpose. So to avoid the above scenario, /tmp use sticky bit.

I also created two file with different user in this folder having permission 777.

Now turn on the sticky bit on this

Now what happens if one user(abhi) want to rename the 2nd user(anshu)

The origin of the sticky bit

On Linux, the sticky bit only has the use described above, on directories. Historically, it was used for something completely different on regular files, and this is where the name comes from.

When a program is executed, it takes time to load the program into memory before the user can actually start using it. If a program, for example an editor is used frequently by users the the start-up time delay was an overhead back then.

To improve this time delay, the sticky bit was introduced. The OS checked that if sticky bit on an executable is ON, then the text segment of the executable was kept in the swap space. This made it easy to load back the executable into RAM when the program was run again thus minimizing the time delay.

Modern systems such as Linux manage their cache of executables and other files automatically and don’t need the sticky bit for that.

Источник