(null).1001.1001
What is this folder? Where does it come from?
drwxrwxrwx 49 appusr appusr 4096 Jan 7 21:52 (null).1001.1001
I think it has something to do with Mr. Root impersonating Mr. AppUsr in a background task, but I posted to AskUbuntu last week, and nobody there recognized it.
Why am I asking? Well ...
On an Ubuntu box, I have a restricted-access applications user who is uid 1001 and gid 1001. Root launches Rserve under that user during boot. The Rserve session is writing into a Windows CIFS share. All seems to be functioning as intended ...
I'm finding these folders peppered throughout the application user's file tree:
drwxrwxrwx 49 appusr appusr 4096 Jan 7 21:52 (null).1001.1001
I'm finding these subfolders in various folders. Each of these subfolders is different, but they seem to contain partial temporary files, like stuff that I extracted from a tarball, or partial pdf writes.
My primary interest in these folders is that I've found that sometimes I need them and don't have them. There's a particular operation can work or fail depending on whether or not this folder is present. When writing a PDF from inside a knitr document that I call remotely from Rserve, I get this error message
## Error in plot.new(): cannot open file '', reason No such file or directory
I can't find an R reason for this, and it works when called from an rstudio-server session or from a Windows Rstudio IDE, but when called from Rserve, it seems to depend on having that folder present in the filesystem, and I'm quite sure that I didn't put it there! What is it?
Related
I access my Google Drive via the terminal using gdfuse. There is a directory that exists, but I can't seem to access via the terminal:
I have a directory called 'papers'. Within that I want to access 'instructions'. When I do ls -ltr I see:
?????????? ? ? ? ? ? instructions
drwxrwxr-x 2 user user 4096 Jun 12 2017 my_docs
-rw-rw-r-- 1 user user 3923 Jul 25 2017 bs237-procedure.txt
with the word instructions appearing in red. And if I try to cd instructions I am told bash: cd: instructions: No such file or directory.
However if I use a browser to go into my Google Drive, I can access the directory 'instructions' and the files within it no problem.
I was searching and I reached this answer, hope it works for you!
To read a file, its read permission needs to be set. However, to read a directory and the listing of its files, both the read and the execute permissions need to be set. If they aren't, you get weird errors like the ones you're experiencing.
To set the read permission on files and the read and execute permissions on directories recursively, use this command:
chmod -R a+rX directoryname
and link to that page: https://askubuntu.com/questions/243999/why-do-question-mark-characters-appear-when-changing-the-permissions-of-director
edit : you can change the folder name, again I saw this on the internet and it seems to work!
I'm trying to get the symbolic link from other user.
My file is located in /home/serviceA/logs/a.txt And I want to create a symbolic link to /home/centos/logs/a.txt.
Here is my command I ran as root user:
ln -s /home/serviceA/logs/a.txt /home/centos/logs/a.txt
I see the red color of filename. And I still get the permission denied error
The error is lrwxrwxrwx 1 root root 47 Feb 12 01:49 /home/centos/logs/a.txt -> /home/serviceA/logs/a.txt
Eventually, I want to forward the /home/centos/logs/a.txt log file to the Splunk.
Why am I getting the permission error after creating the symbolic link? And how do I fix it? (chmod 777 didn't help)
Unfortunately, that isn't how symlinks work on Linux systems. You can't create a symlink to a file, then change the permissions on the symlink and have it change the permissions of the actual file. Think of the security issues with this approach!
If you want Splunk to be able to monitor /home/serviceA/logs/a.txt, you will need to either:
change the file to be world readable (chmod a+r /home/serviceA/logs/a.txt), OR
add splunk (assuming Splunk is running as user splunk) to the group that owns the file, and make the file group readable (chmod g+r /home/serviceA/logs/a.txt), OR
run Splunk as root, BUT THIS IS VERY BAD, DO NOT DO THIS IN PRODUCTION, ONLY DO THIS FOR TESTING, AND EVEN THEN, ITS VERY BAD
I saw the info on finding the name of my temp directory in this question.
The problem I'm having is that my Appdata/Local/temp/[Rtmpxxxx] directory is being deleted during an R session longer than 1 or 2 days. I have turned off all automatic temp deletion actions that Windows 10 can take. There's nothing in Rprofile.site or .Renviron related to temp directory or files.
Any ideas what I need to turn off or modify to keep the Rtmp directory from being deleted?
You could move your temp directory to another folder (outside the win10 temp folder)
e.g. with write("TMP = '<your-desired-tempdir>'", file=file.path(Sys.getenv('R_USER'), '.Renviron'))
If it is still being deleted, it is rather unlikely that Win10 deletes it.
edit by the OP
Depending on [something mysterious], the same command above should be used to create TEMP and TMPDIR as discussed here
I am trying to move a Wordpress installation through svn but I am having problems.
Moving through FTP (Filezilla, copy to desktop then copy to new location on server) works perfectly.
Moving it using cp and mv in SSH works perfectly too.
Doing svn co <url> to checkout a copy of the repository results in 500 Internal Server Error and I can't fix it no matter what... recreating the .htaccess, deleting the plugins folder (no wp-admin access either), deleting the specific theme, etc.
The only difference I can find between my Wordpress folder that's been copied through FTP or SSH and the Wordpress folder created through the svn checkout is this (seen when doing ls -l in SSH):
Moved through FTP/SSH:
drwxrwxr-x 6 suddenm2 suddenm2 4096 Nov 14 19:35 wordpress-folder
Svn checkout:
drwxr-xr-x 5 suddenm2 suddenm2 4096 Nov 14 19:21 wordpress-folder
What exactly do the "5" and "6" mean, and what could the difference in file permissions mean? Thank you
The "5" and "6" mean the number of directories inside the directory, or the number of hard links pointing to the file if it is a file.
You have different numbers of directories between the 2 copy. You probably should check if you are missing anything in the svn checkout.
I'm trying to change the permissions of a few files that are used with a webpage I'm uploading to my site. I'm using the Unix command line to do it.
I've tried two commands:
chmod 755 index.html
chmod 644 index.html
But I get the message
chmod: WARNING: can't access index.html
after using these commands for some reason, and I have no idea why... initially I though it might be because I had the file open in a couple of programs (text editor and web browser), but I've closed these down, and I'm still getting the same problem... any idea why, and how I can set the permissions correctly so that the file will be viewable by anyone on the web, but only editable by me?
Cheers!
Here's a link that looks similar to your problem but it's on Solaris:
http://www.unix.com/solaris/45229-unable-chmod-file-directory.html
The solution is on pg 2 of this thread but the Cliff's note version of the solution is the person found that something else was mounting at that directory. It showed up when they ran
df -k /their_dir_location
Hope this helps.
another possible issue is ... if you are using solaris zones .. the directory visiable in more than one zone but only one zone has write abilities.