Sami Liedes sami.lie...@iki.fi writes:
$ stap --use-server localhost -v -e 'probe begin {}'
FWIW, I don't think this does what you'd imagine it does. Systemtap
seems to be very picky about parameter syntax; in this command line,
Good catch. Fortunately the server still works:
lindi2:~$ stap
On Sat, Jan 07, 2012 at 10:22:36PM +0200, Timo Juhani Lindfors wrote:
Hi,
these steps seem to work for me:
[...]
$ stap --use-server localhost -v -e 'probe begin {}'
FWIW, I don't think this does what you'd imagine it does. Systemtap
seems to be very picky about parameter syntax; in this
Hi,
2012/1/7 Timo Juhani Lindfors timo.lindf...@iki.fi:
Ritesh, we need to think what we want to do with stap-server. Perhaps
modify stap-server package to create a stap-server user and group and an
init script which is disabled by default?
Just an advice regarding the username. It is not a
Hi,
Teodor MICU mteo...@gmail.com writes:
Just an advice regarding the username. It is not a common practice to
set NAME-server as a username for any server/daemon. Instead use just
NAME, in this case 'stap' although I prefer 'systemtap' to avoid
confusion.
Good point. However, the package
2012/1/8 Timo Juhani Lindfors timo.lindf...@iki.fi:
Good point. However, the package is already named systemtap-server so
stap-server or systemtap-server would sound logical still?
My advice was only for the username, not for the package name or
service name in init.d. These should remain the
Hi,
Teodor MICU mteo...@gmail.com writes:
My advice was only for the username, not for the package name or
service name in init.d. These should remain the same unless there is
some other reason to rename them.
Also do note that systemtap already uses two groups, stapusr and
stapdev. Adding a
2012/1/9 Timo Juhani Lindfors timo.lindf...@iki.fi:
Also do note that systemtap already uses two groups, stapusr and
stapdev. Adding a group named stap or systemtap would be quite
confusing here.
I think you should not add another group, but instead use one of these
- probably 'stapusr' for
Teodor MICU mteo...@gmail.com writes:
What is the technical reason to have these two different groups?
Users in stapusr group can execute approved (signed or root-owned)
systemtap scripts without having to be root. Users in stapdev group can
execute arbitrary systemtap scripts. Reusing these for
Package: systemtap-server
Version: 1.6-1
Severity: normal
stap-server start, as documented in the stap-server(8), does not seem
to work at all.
First, the -u option fails due to missing runuser (which comes in
coreutils, but not in Debian's coreutils for some reason):
Hi,
ack, I can reproduce these also with git version.
Ritesh, we need to think what we want to do with stap-server. Perhaps
modify stap-server package to create a stap-server user and group and an
init script which is disabled by default?
I'm not very comfortable at providing any kind of
Hi,
these steps seem to work for me:
$ sudo adduser --system --group --home /var/lib/stap-server --disabled-login
stap-server
$ sudo mkdir /var/log/stap-server
$ sudo chown stap-server:stap-server /var/log/stap-server
$ sudo -u stap-server /usr/lib/systemtap/stap-serverd -r 3.0.0-1-amd64 -a
On 01/07/2012 07:59 PM, Timo Juhani Lindfors wrote:
Ritesh, we need to think what we want to do with stap-server. Perhaps
modify stap-server package to create a stap-server user and group and an
init script which is disabled by default?
If your steps in the other email work fine, we could go
12 matches
Mail list logo
