> '-lp' is a short for '-l -p'
Right, i had tested it with a regular user (where -p won't work)... i
stand corrected.
Nuno
--
() ascii ribbon campaign - against html e-mail
/\ ascii-rubanda kampajno - kontraŭ html-a retpoŝto
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
wit
On Sat, Apr 18, 2009 at 12:24:23PM +0100, Nuno Magalhães wrote:
> On Sat, Apr 18, 2009 at 12:04, Tzafrir Cohen wrote:
> > netstat -lp | grep tftp
>
> I think you mean:
>
> netstat -l -p | grep tftp
'-lp' is a short for '-l -p'
>
> Otherwise you won't get the ports part. An alternative (tha
On Sat, Apr 18, 2009 at 12:04, Tzafrir Cohen wrote:
> On Fri, Apr 17, 2009 at 07:59:22PM +0100, Nuno Magalhăes wrote:
>
>> # netstat -l | grep ftp
>> udp 0 0 *:tftp *:*
>
> For future reference: at this point you should have run:
>
> netstat -lp | grep tftp
I think y
On Fri, Apr 17, 2009 at 07:59:22PM +0100, Nuno Magalhães wrote:
> # netstat -l | grep ftp
> udp0 0 *:tftp *:*
For future reference: at this point you should have run:
netstat -lp | grep tftp
which would have exposed the guilty process
--
Tzafrir Cohen |
> I only found it by doing "netstat" -- because it's inetd
> triggered, the "bad" tftp doesn't show up in the process list.
Yup, i was wondering why was the socket misteriously spoken for and
yet netstat -l |grep ftp showed nothing... Solved it already, thanks.
Nuno
--
() ascii ribbon campaig
On Friday 17 April 2009 12:14:52 Nuno Magalhães wrote:
> Hi, i'm having a slight issue following this article [1]. My client
> will boot through PXE and find the host, then it won't find an image
> and keeps on showing TFTP timeouts.
I ran into this recently -- it turned out that the non-hpa TFT
Turns out it was mostly user-error.
1) i was having issues starting tftpd-hpa through /etc/init.d
- the tftp daemon was already being run by inetd, i was unaware of
that, got it to run stand-alone since it's a one-time job anyway and
i'm goofing around.
2) dhcp3-server gave the client the ip, but
2009/4/17 Nuno Magalhães :
>> Very odd. Could be that it is listed in /etc/inetd.conf and
>> is just not running at the instance that you look ..?
Well, yes, it was being controlled by inetd and some rtfm-ing later i
thought it better to be stand-alone. So, it's running: i get the
prompt back a
> Very odd. Could be that it is listed in /etc/inetd.conf and
> is just not running at the instance that you look ..?
It's actually the only thing active in that file, all others are comented out.
tftp dgram udp waitroot /usr/sbin/in.tftpd
/usr/sbin/in.tftpd -s /var/lib/tf
On Fri Apr 17, 2009 at 19:59:22 +0100, Nuno Magalh??es wrote:
> Still no results... why wouldn't a process list itself? The socket is
> there but there's no process listening on it?
Very odd. Could be that it is listed in /etc/inetd.conf and
is just not running at the instance that you look .
On Fri, Apr 17, 2009 at 19:42, Steve Kemp wrote:
> (ie. There is another tftpd deamon already running.)
I assumed that, but i find none.
> No. The message is talking about a network socket. Kill the existing
> process and all will be well.
There is a network socket:
# netstat -l | grep ft
On Fri Apr 17, 2009 at 19:34:52 +0100, Nuno Magalh??es wrote:
> > Usually I'd say look at /var/log/daemon.log - if that doesn't
> > work I'd add "set -x" to the init script and see how far it
> > gets.
>
> Ah, daemon.log it's a socket issue:
>
> Apr 17 19:12:57 box in.tftpd[15899]: cannot bin
> Usually I'd say look at /var/log/daemon.log - if that doesn't
> work I'd add "set -x" to the init script and see how far it
> gets.
Ah, daemon.log it's a socket issue:
Apr 17 19:12:57 box in.tftpd[15899]: cannot bind to local IPv4 socket:
Address already in use
There's nothing "pending" o
Hi
> Hi, i'm having a slight issue following this article [1]. My client
> will boot through PXE and find the host, then it won't find an image
> and keeps on showing TFTP timeouts.
did you check if tftp is running on you server ?
# ps -A | grep tftp
> The thing is, to use the articles example,
On Fri Apr 17, 2009 at 17:14:52 +0100, Nuno Magalh??es wrote:
> The thing is, to use the articles example, instead of:
> r...@itchy:~# /etc/init.d/tftpd-hpa start
> Starting HPA's tftpd: in.tftpd.
> r...@itchy:~#
itchy! I remember that machine ..
> I'm using unstable's tftp-hpa 0.49 and don't
15 matches
Mail list logo
