| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This isn't completely possible because some interfaces cause
syntax or load errors. We need to keep a list of interfaces
to filter out to get something that loads.
This adds gxpp as a requirement to build qarsh.
|
|
|
|
| |
This will prevent temp files from being packaged
|
|
|
|
| |
We generate the policy based on which services we want to test.
|
|
|
|
|
|
| |
In rare cases the getpwuid() call will fail because of a YP
or LDAP timeout. If we're not using the local username we
shouldn't even bother looking it up.
|
| |
|
|
|
|
|
|
| |
Cache the results from the rstat packet and use that file size
during the following sendfile so we don't send more than qacp
is expecting. This should allow us to qacp root@host:/var/log/messages
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
If qarshd is broken enough that it can't load libxml2.so, it
won't return an XML packet which we can parse. set_remote_user()
really needs to error out of we didn't get a packet back.
|
|
|
|
|
| |
A quarter of a second may be too short for some connections.
Increasing it to half a second should make it more reliable.
|
|
|
|
| |
Make btimec return proper exit codes so it is more useful in scripts.
|
|
|
|
|
| |
Freeing from the middle of an allocated string is not right.
Keep a pointer to the strdup so we can free it correctly.
|
|
|
|
|
|
|
|
|
| |
I don't know how, but I found one instance of qarsh looping
through the pselect loop with a one second timeout. If the command has
exited and the output file descriptors are all closed, we fall onto
this continue which prevents us from getting to the break at the end of
the loop. The only thing the continue skips over is that check which we
really should check, so remove the continue.
|
| |
|
|
|
|
|
| |
When we tried it out on Fedora 10, it was sending responses to IPv6
addresses and returning ENETUNREACH (Network is unreachable).
|
| |
|
|
|
|
|
|
| |
All the actions which need to be done before we exit are done after the
pselect. Waiting until after the next pselect can cause us to sit for
a second before we exit, which slows down things which use qarsh.
|
|
|
|
| |
Interactive logins are definitely NOT supported by qarsh.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We need to test all exit conditions at once so we fall back into the
hbeat code. I was falling into a case when running "reboot -fin &"
where the command would exit, but the sockets would not close and we
weren't getting to hbeat() to detect the reboot.
In another case which I can't completely explain, we were getting a
double-free error from glibc in the qpfree() at the end of
run_remote_cmd(). Instead of waiting until the very end to read the
exit status, save it off as soon as we get the packet and use
cmd_exitted to determine if we have an exit code or if something went
horribly wrong.
|
| |
|
|
|
|
|
| |
A previous commit added tmprstatp, which wasn't being checked just after
it was assigned.
|
|
|
|
|
|
|
| |
It turns out the boot time being returned to btimec is has not been
correct for quite a while. There was probably a change to HZ which
isn't reflected properly in _SC_CLK_TCK. This needs some more error
checking, but it works for now.
|
| |
|
|
|
|
|
|
| |
sendfiles should be re-written and broken into single file and multi-file cases to make this cleaner.
Signed-off-by: Dean Jansa <djansa@redhat.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
commands so qarsh exits.
|
| |
|
|
|
|
| |
quickly that we do a hbeat then go back to the pselect.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
When running rsync on an existing directory structure, rsync may be too
busy to read everything that qarsh is writing to it from the remote
rsync daemon. Create a buffer for each of stdin, stdout, and stderr
and keep it around until we are able to write it, holding off further
reads until it can be written. We still don't handle partial writes.
|
|
|
|
| |
For those that can't configure syslog properly while debugging other things.
|
|
|
|
| |
but lets you in. Don't bother checking the return of chdir().
|
| |
|
|
|
|
| |
has exitted and we've processed all the output.
|
|
|
|
|
| |
help get all output before we exit. There is still a race if the cmdexit
packet returns before all output where we could truncate output.
|
|
|
|
| |
the address in the hbeat struct instead of the name.
|