I don’t know if it’s a real bug in opensuse 13.1 x64, but some script is generating a folder with strange name “%{LOGFILEDIR” and a file named as “}” with root permission, no problem to delete both but they will come back again, I think something is broken somewhere…
Is there some way to find it???
Thanks in advance,
Edwin
You posted to the wrong place please asked to be moved to a more appropriate locations. Use the triangle at bottom of the text window to alert a moderator and ask to be moved.
This is CLOSED and will be moved to Applications.
Moved from Unreviewed Howto and FAQ and open again.
Hello and welcome here.
Please always try to use the (sub)forunm that fits best to your problem. The Unreviewed Howto and FAQ, where it says in bold script: “Do not ask technical Questions here” isn’t the right place to ask technical questions.
Then you tell a story, but we like to see computer facts. Thus when you say there is a “folder” and a “file”, please post the output of the command
ls -l
of the directory and the file showing them and their properties. Then we can see for ourselves.
Because you are new here and thus unaware how to post these computer texts in the way as I showed you here, use the # button in the tool bar of the post editor to get CODE tags in your post. Then copy/paste from your terminal the prompt, the command, the output and the next prompt in between te CODE tags.
Obviously something is creating a log directory named “%{LOGFILEDIR }” instead of “%{LOGFILEDIR}” (i.e. there’s a superfluous space).
You might find it by grepping all files on your hard disk for that string.
Maybe start in the cron directories:
grep -R "%{LOGFILEDIR }" /etc/cron*
This should find it in any case, but will take looong:
grep -R "%{LOGFILEDIR }" /
But maybe the content of those files (“%{LOGFILEDIR” and/or “}”) would give a clue to what creates them?
Btw, I haven’t seen this on my systems.
On my system, these folders appear at runtime of applet to update the OS, and how to fix it I do not know also. 
… and this folders always is empty.
And what Desktop Environment are you using?
I don’t see them on any of my (KDE) systems.
So I doubt that’s a bug in KDE’s update applet or PackageKit.
… and this folders always is empty.
Of course.
Because they are not intentionally created and therefore are not used for anything.
KDE forever… )
I think you’re right…
And i don’t know a moment when these folders were born first time…
Well, they could be created by some buggy install script in some package.
Have a look at the creation date/time of those folders, and then look into /var/log/zypp/history to see what package has been installed at that time.
But this is just a guess.
Another thing to try I already posted earlier.
I configured my audit daemon some time ago and now found next sequences:
— example 1 —
— auditd log file
type=PATH msg=audit(1403081658.732:11988): item=1 name=“%{LOGFILEDIR” inode=393218 dev=08:02 mode=040755 ouid=0 ogid=0 rdev=00:00
— obfuscate time is
Wed Jun 18 11:54:18 2014
— /var/log/zypp/history:
2014-06-11 11:52:34|install|libsolv-tools|0.4.2-11.1|x86_64||repo-update|c228c18ac62f655b725aeea2e3ce417b1c99e811ed3d76227a2d9cdef33c630d|
2014-06-11 11:52:35|install|zypper-aptitude|1.9.16-22.2|noarch||repo-update|78ebf606c14ebe07b55ef46f6b0f2b1e2adb69676fac15bcd5c21329cbf12cfd|
2014-06-11 11:52:35|install|zypper-log|1.9.16-22.2|noarch||repo-update|d40a3f82f47b6983ee0ae7da021880463db38858afcc3a2aa4456c197a2409c8|
2014-06-11 11:52:47|install|libzypp|13.10.2-19.6|x86_64||repo-update|cd62ea7cd7d3669313b1019480f06c29e16d35e3d056b9ea87b5414f63e0621a|
2014-06-11 11:53:06|install|zypper|1.9.16-22.2|x86_64||repo-update|df77756d2115b8ba5b9873196a84a13ebe1ca2b887f422e1dea97344d67b0191|
2014-06-11 11:59:47|install|wine-mp3|1.1.39-13.5|i586|root@xxxxxxxxxxxx.xxx|PackMan|93c1808a30d4e77319386bfe16fa183839c70f5de88a85836d52d8dfc6b1237c|
2014-06-11 11:59:48|install|libgstreamer-1_0-0|1.2.4-3.8|x86_64|root@xxxxxxxxxxxx.xxx|PackMan|56eb241f91ec25044c7b8dc2a33b27ac338e50bff8d52ca8991d6f1abbdcc26d|
— example 2 —
— auditd log file
audit.log:type=PATH msg=audit(1403529525.621:27140): item=1 name=“%{LOGFILEDIR” inode=393218 dev=08:02 mode=040755 ouid=0 ogid=0 rdev=00:00
— obfuscate time is
Mon Jun 23 16:18:45 2014
— /var/log/zypp/history:
2014-06-23 16:18:38|install|gstreamer-plugins-bad|1.2.4-6.22|x86_64|root@xxxxxxxxxxxx.xxx|PackMan|3a3a2366c19d8f59faf24cf6925c1ad35d0c76b1743b1ce03984748790f50afa|
2014-06-23 16:18:39|install|gstreamer-plugins-bad-lang|1.2.4-6.22|noarch|root@xxxxxxxxxxxx.xxx|PackMan|07ed43612e033030fc65826ae9da4014d0204d858915b74727c8c09ad7ce7a10|
2014-06-23 16:18:46|install|freeswitch|1.2.23-1.14|x86_64|root@xxxxxxxxxx.xxx|PackMan_Extra|f591f0b5509bf56800b219716b077ecec99e2d21e52775051a67684d60bed5ae|
2014-06-23 16:18:47|install|freeswitch-codec-mp4v|1.2.23-1.14|x86_64|root@xxxxxxxxxxxx.xxx|PackMan_Extra|a8bdf18bd18772d92323159b715ba6259bfaaaee73a970f9b00d20e671a174a1|
2014-06-23 16:18:47|install|freeswitch-codec-h26x|1.2.23-1.14|x86_64|root@xxxxxxxxxxxx.xxx|PackMan_Extra|65e823cbe580975e7075bde0e17de9b27760a56d5c0e9759d603d2d4c5bc4ca3|
2014-06-23 16:18:52|install|darktable|1.4.2-1.12|x86_64|root@xxxxxxxxxxxx.xxx|PackMan_MM|b6b2e908c91704787e17812f4d29b41ebc1744403456e1eb3cdfcdef3de0aa75|
xxxxxxxxxxx.xxx -> is my hostname
Looks like it’s not in the package script…
Thank you for the idea about zypper logfile, but it does not help us…
/var/lib/rpm/Packages have a nice code: “mkdir -p /var/run/freeswitch %{LOGFILEDIR>}”…
???
/var/lib/rpm/Packages is the RPM database, i.e. the database of all installed packages.
It does not have any code.
That said, maybe the packages’ postinstall (and other) scripts might be stored in the database as well, I’m not sure. (would make sense, because otherwise rpm wouldn’t be able to run the postuninstall scripts…)
So if you found this in /var/lib/rpm/Packages, it is indeed most likely some package install script.
Apparently this would be the package freeswitch. Where did you install it from? (it isn’t part of the distribution)
rpm -qi freeswitch
I suppose Packman, I do find this in their specfile:
%post
%{?run_ldconfig:%run_ldconfig}
# Make FHS2.0 happy
# %%{__mkdir} -p /etc/opt
# %%{__ln_s} -f %%{sysconfdir} /etc%%{PREFIX}
%if !0%{?suse_version}
chkconfig --add freeswitch
%else
%fillup_and_insserv
%endif
mkdir -p %{RUNDIR} %{LOGFILEDIR>}
chown freeswitch:daemon %{LOGFILEDIR} %{RUNDIR}
(seems to be a typo…)
The next step you should do is tell the package maintainers so they can fix it.
In the case of Packman this would be either their mailinglist or their bugtracker:
http://lists.links2linux.de/cgi-bin/mailman/listinfo/packman
http://bugs.links2linux.org/
PS:
Obviously it did show the culprit… 
Hi, Edwin again.
Thank you guys for replies!!!
It’s strange, but I posted on july, since that no notification came until today.
After I posted here I tried a fresh installation with a new downloaded disk image, the empty folder “{%LOGFILEDIR” and the empty file “}” it wasn’t created, I was thinking that some script tried to create a folder “{%LOGFILEDIR}”, but some character between the “R” and “}” broke them in two creating a file named “}”. I don’t know how to track things like this yet :P, but thank you so much guys.
Actually I’m running openSUSE Factory flawlessly and happy!!!
How can I close/delete this post?
I’d guess that kind of error might be logged in your system logs.
Maybe the following will display something useful?
cat /var/log/messages | grep %{LOGFILEDIR
TSU
I’m not trying to be kewl or perfect or something but i thought i had pointed out on the other threads on this forum that cat | grep is always wrong.
If you do
cat file
then it is right to do
grep file
The correct is sypnosis is
grep [OPTION]... PATTERN [FILE]...
Again i’m not trying to be kewl just pointing out somethings. Thank you.
That’s because nobody posted anything in this thread during that time.
After I posted here I tried a fresh installation with a new downloaded disk image, the empty folder “{%LOGFILEDIR” and the empty file “}” it wasn’t created, I was thinking that some script tried to create a folder “{%LOGFILEDIR}”, but some character between the “R” and “}” broke them in two creating a file named “}”. I don’t know how to track things like this yet :P, but thank you so much guys.
I already told you in my previous post that there’s a typo in the postinstall script of the package freeswitch which causes those directories to be created.
And again, this should be reported to the packagers so they can fix it.
Actually I’m running openSUSE Factory flawlessly and happy!!!
If you’d install the package “freeswitch”, you will see the same thing again.
How can I close/delete this post?
You can’t.
No, it won’t.
Why should it?
And the mystery is solved already anyway.