openshift UID permissions for files different on deployment than pod 3.11 - openshift

curious if anyone can explain this one to me, I'm using ocp 3.11 and NFS as the persistence for my containers...
if I run the container as a Deployment I end up with what looks like the correct permissions (e.g. arbitrary UID):
drwx------. 20 1000060000 nfsnobody 4096 Nov 5 10:29 alpha
however, if I run the same container as a simple pod I end up with the USER as owning the files:
drwxr-x---. 3 26 26 41 Nov 5 11:29 lastone
i would have thought the pod would write with the same UID as the deployment above. I'm probably missing something simple here and any suggestions would be appreciated.

Related

Anaconda lib duplicates of libonedal_core

I'm looking through my Anaconda folders noticing what seem to be many duplicates. All these dupes are modified at the same time, all seem to have a version convention. They are not symlinks.
In ~/opt/anaconda3/lib and ~/opt/anaconda3/pkgs/dal-2021.5.0-hecd8cb5_782/lib
Are these in fact dupes? If yes, what's the safest way to remove the dupes? I've already run conda clean -ap and
These files are very likely symbolic links (softlinks) to a single file. It would be better to examine such files with a ls -lh command from a shell, rather than through a GUI. For example, if I look at libmamba* in my base environment, I see
$ ls -lh ~/miniconda3/lib/libmamba*
-rwxrwxr-x 2 mfansler staff 3.2M Aug 23 16:32 libmamba.2.0.0.dylib
lrwxr-xr-x 1 mfansler staff 20B Sep 29 17:05 libmamba.2.dylib -> libmamba.2.0.0.dylib
lrwxr-xr-x 1 mfansler staff 20B Sep 29 17:05 libmamba.dylib -> libmamba.2.0.0.dylib
where the arrows (->) represent symbolic links. Also notice how those are only 20 bytes.

403 Forbidden - Mac Local Host

I am attempting to set up an AMP stack in order to do some basic web design with HTML 5, PHP, CSS, Apache, etc. I have done this on a PC but I am having trouble setting it up on my new Mac. I am trying to follow these steps (http://coolestguidesontheplanet.com/get-apache-mysql-php-and-phpmyadmin-working-on-osx-10-11-el-capitan/) but at the end of the first set of instructions I can't get the files to show and am getting a 403 error. Can someone please point me in the right direction or give me a good resource. Thank you.
Here is my current permissions on the file:
total 16
-rw-r--r-- 1 root wheel 96 Jan 10 13:39 Guest.conf
-rw-r--r-- 1 root wheel 132 Jan 20 15:52 username.conf
The way I found easiest was to do the following:
cd /filepath/to/thing/you/want; php -S localhost:8000
and then visit localhost:8000 on your computer.
Hoped this helps, as this is my first answer on StackOverflow.

Message Archive Management Plugin (Prosody) can't open archive

I'm trying to get Message Archive Management ( mam ) on a prosody server
working.
I tried it with SQLite3, MySQL and PostgreSQL.
Always this log:
Oct 20 14:56:21 general info Hello and welcome to Prosody version 0.9.7
Oct 20 14:56:21 general info Prosody is using the epoll backend for connecti$
Oct 20 14:56:22 localhost:mam error Could not open archive storage
The archive is existing in /var/lib/prosody/.

Error 403 wont load any files in project folders

Can someone please explain with clear step by step instructions to a noobie, why is my console giving me these errors for some of my files on a project? I usually get them for external style sheets sometimes images and external .js documents.
Makes no sense to me.
Console shows Error: 403 Forbidden for each of them...
My noobie intuition says something is not right with my permissions for my sites directory or something among these lines. I dont know how to check
If you are using a LAMP stack for web server then you can face that problem.
First check the permission of all the files in the subsequent directory -
Let say that these are four external js in your html file like as :-
<script src="/js/file1.js"></script>
<script src="/js/file2.js"></script>
<script src="/js/file3.js"></script>
<script src="/js/file4.js"></script>
and you are getting errors for file1.js and file2.js then goto the js directory and check their permissions :-
user#host js $ ls -la
total 188
drwxrwxr-x 2 user user 4096 Jul 19 01:51 .
drwxrwxr-x 6 user user 4096 Jul 19 01:39 ..
-rw-rw-r-- 1 user user 55258 Feb 13 2014 file1.js
-rwxrw-r-- 1 user user 55258 Feb 13 2014 file2.js
-rwxrw-r-- 1 user user 55258 Feb 13 2014 file3.js
-rw-rw-r-- 1 user user 55258 Feb 13 2014 file4.js
-rw-rw-r-- 1 user user 29110 Feb 13 2014 bootstrap.min.js
If required change their permission with chmod and chown command.

Having description and contact at Mercurial web page

Currently, I am in the progress of migrating CVS to Mercurial.
http://jstock.hg.sourceforge.net/hgweb/jstock/
I would like to have contact and description information in the mercurial page.
I look at https://www.mercurial-scm.org/wiki/PublishingRepositories#Putting_useful_information_in_the_index_page
But, it seems that, modification on C:\Projects\jstock\.hg\hgrc doesn't have any effect at all. push will not update anything in sourceforge server.
So, does this mean the only way is to remote access to sourceforge mercurial server and modify the hgrc file manually?
I try to ssh to the remote machine.
[yccheok#shell-22003 .hg]$ pwd
/home/scm_hg/j/js/jstock/jstock-cloud/.hg
[yccheok#shell-22003 .hg]$ ls -al
total 56
drwxrwsr-x 3 yccheok jstock 1024 Nov 30 15:29 .
drwxrwsr-x 3 yccheok jstock 80 Nov 30 15:13 ..
-rw-rw-r-- 1 yccheok jstock 57 Nov 30 15:13 00changelog.i
-rw-rw-r-- 1 yccheok jstock 93 Nov 30 15:29 branchheads.cache
-rw-rw-r-- 1 yccheok jstock 23 Nov 30 15:13 requires
drwxrwsr-x 3 yccheok jstock 1024 Nov 30 15:29 store
-rw-rw-r-- 1 yccheok jstock 317 Nov 30 15:29 tags.cache
-rw-rw-r-- 1 yccheok jstock 7 Nov 30 15:29 undo.branch
-rw-rw-r-- 1 yccheok jstock 0 Nov 30 15:29 undo.dirstate
[yccheok#shell-22003 .hg]$
But not able to find hgrc file.
The .hg/hgrc file contains local settings and is not itself a versioned file. These settings do not travel from one repository to the other by hg clone, hg push or hg pull commands.
If you want to edit the hgrc file of your source forge repository, you have to use Sourceforge's interactive shell service.
My guess would be that the sourceforge server doesn't consider your repo's .hg/hgrc file due to trust rules. Their webserver user would need to have a trust block saying they trust .hgrc files from you, which is a risk as it allows you to have code executed as their webserver user.
If there's a way to do this the solution is going to come from somewith with strong sourceforge-fu, not mercurial-fu.