Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: rhermsen on March 30, 2024, 07:55:44 AM
-
This is on TCL-15.0 x86
I do see similar messages in /var/log/messages for x86_64 (CP64 boots faster in graphical mode so likely I missed to see these messages while booting).
chown: warning: '.' should be ':': 'root.staff'
chown: warning: '.' should be ':': 'root.staff'
chown: warning: '.' should be ':': 'tc.staff'
One is coming from the install script part of extension Xlibs.
And the other two look to come from the wbar extension from file: /usr/local/bin/wbar_setup.sh
/var/log/messages
Mar 30 11:30:46 box authpriv.notice sudo: tc : TTY=console ; PWD=/mnt/vda1/tce/optional ; USER=root ; COMMAND=/usr/local/tce.installed/Xlibs
Mar 30 11:30:46 box authpriv.notice sudo: tc : TTY=console ; PWD=/mnt/vda1/tce/optional ; USER=root ; COMMAND=/bin/chown -R root.staff /usr/local/tce.installed
Mar 30 11:30:48 box authpriv.notice sudo: tc : TTY=console ; PWD=/mnt/vda1/tce/optional ; USER=root ; COMMAND=/bin/cp /usr/local/share/wbar/dot.wbar /usr/local/tce.icons
Mar 30 11:30:48 box authpriv.notice sudo: tc : TTY=console ; PWD=/mnt/vda1/tce/optional ; USER=root ; COMMAND=/bin/chown root.staff /usr/local/tce.icons
$ sh -x /tmp/tcloop/Xlibs/usr/local/tce.installed/Xlibs
+ read USER
+ '[' -f /home/tc/.xsession ]
+ '[' -f /home/tc/.setbackground ]
+ '[' -f /home/tc/.Xdefaults ]
+ '[' -d /opt/backgrounds ]
+ sudo chown -R root.staff /usr/local/tce.installed
+ sudo chmod -R 775 /usr/local/tce.installed
sh -x /usr/local/bin/wbar_setup.sh
..
+ sudo chown root.staff /usr/local/tce.icons
..
I remember this change of chown from the far past.
If I'm not mistaken this was to prepare for allowing (part of the) email addresses as username.
-
Xlibs/wbar modified and reposted to tc-15.x x86/x86_64 repos - thanks for reporting this.
-
@Juanito
Thanks a lot for fixing this.
I was still looking into another message I see. Guess just an 'info' message, and likely no need to 'suppress':
nohup: redirecting stderr to stdout
I suspect this is coming from:
$ sudo grep -rin nohup /usr
/usr/local/bin/wbar.sh:13: nohup wbar >/dev/null &
Don't know if it is expected that standard error messages become redirected to standard output after redirecting standard output to dev/null.
Here (https://stackoverflow.com/questions/31759226/nohup-redirecting-stderr-to-stdout-in-ubuntu)a similar behavior is mentioned (and a 'fix' to also redirect stderr to dev/null )
-
Hi Juanito
I just tested this under TC10.
Changing line 13 of wbar.sh from this:
nohup wbar >/dev/null &
To this:
nohup wbar >/dev/null 2>&1 &
will fix it.
-
wbar reposted :)