search

ftnapps / mbsebbs

Debian/Ubuntu Packaging for MBSE BBS
ftnapps.github.com/mbsebbs
GNU General Public License v2.0
5 stars 2 forks source link

Issue with mbtask on armv7 #1

Open kevit opened 8 years ago

kevit commented 8 years ago

Hello I trying to run mbse on armv6l, but i am facing issue with mbtask

socket(PF_INET, SOCK_RAW, IPPROTO_ICMP) = -1 EPERM (Operation not permitted) write(2, "socket init failed, mbtask not i"..., 53socket init failed, mbtask not installed setuid root ) = 53

but ls -lah bin/mbtask -rws--s--x 1 root root 141K Jun 15 10:57 bin/mbtask

is there any ideas why it happened?

kevit commented 8 years ago

Actually I spend some time on that and found that is a strace bug, not a mbtask

Programs that use the setuid bit do not have effective user ID privileges while being traced.

there is another problem,

` mbsebbs@raspberrypi:~/log$ mbtask MBTASK: MBSE BBS v1.0.6 Task Manager Daemon Copyright (C) 1997-2015 Michiel Broek, All Rights Reserved

Can't open logfile "/var/lib/mbsebbs/log/" Can't open logfile "/var/lib/mbsebbs/log/" Can't open logfile "/var/lib/mbsebbs/log/" Can't open logfile "/var/lib/mbsebbs/log/" Can't open logfile "/var/lib/mbsebbs/log/" Can't open logfile "/var/lib/mbsebbs/log/" `

jame commented 8 years ago

How did you install that? It looks like the log files themselves are not defined properly; that's just the log directory itself that's showing the errors. Note that the log file names are defined in 'Edit Global Filesnames' , section 1.3 in mbsetup. The default system logfile would be 'system.log', for instance. If those are defined, then it may be a permissions issue; i.e., the user attempting to run mbtask does not have access to that directory.

kevit commented 8 years ago

Actually, i will be back to this next week, i just built a package and did dpkg -i This problem belongs to the deb package building, because if I building manually everything works

jame commented 8 years ago

I would note that the it still says UNRELEASED in the debian/changelog file, which is meant to indicate that it is not ready yet. (It will change to something like stable when it is.) And one of the issues keeping it UNRELEASED is with getting the programs that require it installed with the proper permissions, like mbtask. Note that installing from the tar ball is fine, as that does install them with proper permissions when done using the standard procedure. Note also that you're installing from the from the git repo rather than from released tarball, use the master branch as that is without the debian directory.